CN116708062B

CN116708062B - Equipment management method and electronic equipment

Info

Publication number: CN116708062B
Application number: CN202211215232.XA
Authority: CN
Inventors: 兰继生; 朱鑫泰
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-09-30
Filing date: 2022-09-30
Publication date: 2024-05-31
Anticipated expiration: 2042-09-30
Also published as: CN116708062A

Abstract

The application provides a device management method and electronic equipment, and relates to the technical field of Internet of things. And the firmware influence on the Internet of things equipment and the first equipment is reduced while the addition of the IOT equipment is supported. The specific scheme is as follows: the first equipment responds to the received first hot spot information and sends a first request to the first server, the first server responds to the first request and sends first data to the first equipment, and the first data comprises equipment discovery communication standards followed by the first Internet of things equipment; the first equipment runs first data and sends a first discovery request to the first Internet of things equipment; after the first equipment receives the first response information, displaying a second interface, wherein the first response information carries equipment information of the first Internet of things equipment; the second interface comprises a first option control, and the first option control is used for displaying equipment information of the first Internet of things equipment; after the first device detects the operation of the user on the first option control, a third interface is displayed, and the third interface comprises the first management control.

Description

Equipment management method and electronic equipment

Technical Field

The present application relates to the field of internet of things, and in particular, to a device management method and an electronic device.

Background

With the development of internet of things (internet of things, ioT) technology, various IoT devices appear in the life of users, which brings convenience to the life of users. Taking an intelligent home environment as an example, IOT devices applied to the intelligent home environment include audio and video devices (such as televisions, loudspeaker boxes and the like), lighting systems, air conditioners, network routers and the like.

Generally, before a user uses various IOT devices, the IOT devices need to be added to a control range of a control terminal (e.g., a mobile phone), so that the user can control the IOT devices through the mobile phone.

However, various IOT devices and handsets are usually from different manufacturers, and in related art, software development kits (software development kit, SDKs) corresponding to the handsets are configured in the IOT devices, and the IOT devices can only be controlled by the handsets under the condition of short for the handsets SDKs.

Obviously, for the manufacturers of IOT devices, configuring the handset SDKs in the IOT devices requires modification of the original firmware of the IOT devices, which undoubtedly increases the workload and cost. In addition, the IOT devices that are sold and not configured with the SDK of the mobile phone cannot be managed by the mobile phone.

Disclosure of Invention

The embodiment of the application provides a device management method and electronic equipment, which are used for reducing the influence on firmware of an IOT device and a control terminal while supporting the addition of the IOT device.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical scheme:

In a first aspect, an embodiment of the present application provides a device management method, which is applied to a first system, where the first system includes a first device and a first server, and the method includes: the method comprises the steps that a first device responds to a first operation of a user, and a first interface is displayed, wherein the first interface is an Internet of things device discovery interface; during the display of the first interface, the first device responds to the received first hot spot information and sends a first request to the first server, wherein the first hot spot information is the hot spot information broadcasted by the first Internet of things device, the first hot spot information comprises a first name corresponding to the first Internet of things device, and the first request comprises the first name and an identifier indicating a device discovery link; the first server responds to the first request and sends first data to the first device, wherein the first data comprises a device discovery communication standard followed by the first Internet of things device; the first equipment runs first data and sends a first discovery request to the first Internet of things equipment; after the first equipment receives the first response information, displaying a second interface, wherein the first response information is fed back by the first Internet of things equipment, and the first response information carries the equipment information of the first Internet of things equipment; the second interface comprises a first option control, and the first option control is used for displaying equipment information of the first Internet of things equipment; after the first device detects the operation of the user on the first option control, a third interface is displayed, wherein the third interface comprises a first management control, and the first management control corresponds to the first Internet of things device and is used for triggering the sending of a control instruction to the first Internet of things device.

In the above embodiment, when the first device needs to discover the first internet of things device, the first data capable of realizing the discovery of the first internet of things device is downloaded from the first server, so that even if the original firmware in the first device does not support the discovery of the first internet of things device, the discovery of the first internet of things device can be realized without updating the firmware version. Meanwhile, when the actual demand occurs, the first device downloads standard data corresponding to the execution link required, so that the invalid occupation of the memory space of the first device is reduced. In addition, the firmware of the first Internet of things equipment does not need to be changed, so that the influence on the firmware of the Internet of things equipment and the original firmware of the first equipment is reduced.

In some embodiments, after displaying the third interface, the method further comprises: the first device responds to a second operation of the user and displays a first interface; during the display of the first interface, the first device responds to the received second hot spot information, and sends a second request to the first server, wherein the second hot spot information is the hot spot information broadcast by the second internet-connected device, the second hot spot information comprises a second name corresponding to the second internet-connected device, and the second request comprises the second name and an identifier indicating a device discovery link; the first server responds to the second request and sends second data to the first device, wherein the second data comprises a device discovery communication standard followed by the second internet-enabled device; the first equipment runs second data and sends a second discovery request to the second internet-connected equipment; after the first equipment receives second response information, displaying a fourth interface, wherein the second response information is fed back by the second internet-connected equipment, and the second response information carries equipment information of the second internet-connected equipment; the fourth interface comprises a second option control, and the second option control is used for displaying equipment information of the second internet-connected equipment; after the first equipment detects the operation of the user on the second option control, a third interface is displayed again, a second management control is added in the third interface, the second management control corresponds to the second internet of things equipment and is used for triggering the sending of a control instruction to the second internet of things equipment, and the second internet of things equipment and the first internet of things equipment come from different manufacturers.

In the above embodiment, even if the first device faces to the internet of things device of different manufacturers, the first device can be added in a similar manner, so as to improve the compatibility of the first device with the multi-manufacturer device.

In some embodiments, after the first device detects the operation of the first option control by the user, in a scenario in which the first device logs in to a first account provided by the first server, the method further includes: the first equipment logs in a second account number provided by a second server, and the second server is a server corresponding to the first Internet of things equipment; the first device sends a second account to the first server, the first server and the second server are instructed to associate the first account with the second account, and after the first account is associated with the second account, the first account in the first server corresponds to the bound internet of things device under the second account.

In some embodiments, after the first device detects the user operation of the first option control, the method further comprises: the first equipment sends a third request to the first server, wherein the third request comprises a first name and an identifier indicating the equipment network distribution link; the first server responds to the third request and sends third data to the first device, wherein the third data comprises the device distribution network communication standard followed by the first Internet of things device; and the first equipment runs the third data, and sends the service set identification and the secret key of the first network to the first Internet of things equipment, and indicates the first Internet of things equipment to join the first network.

In some embodiments, after the first device detects a user operation on the first option control in a case where a first account and a second account have been associated in the first server, the method further includes: the first device sends a fourth request to the first server, wherein the fourth request comprises the first name and an identifier indicating a device binding link; the first server responds to a fourth request and sends fourth data to the first equipment, wherein the fourth data comprises a first interface which is required to be called by the first Internet of things equipment; the first device runs fourth data, a first call request is sent to a first interface of the second server through the first server, the first call request comprises device information of the second account and the first internet of things device, and the second server is indicated to bind the second account and the first internet of things device.

In some embodiments, after the first device detects the user's operation on the first option control in a case where the first account and the second account have been associated in the first server, the method further includes: the first equipment sends a third request to the first server, wherein the third request comprises a first name and an identifier indicating the equipment network distribution link; the first server responds to the third request and sends fifth data to the first device, wherein the fifth data comprises the device distribution network communication standard followed by the first Internet of things device; the first device runs fifth data, and sends token request information to the second server through the first server, wherein the token request information comprises a second account; after receiving the first token information sent by the second server, the first server sends the first token information to the first device, wherein the first token information corresponds to the second account; the first device sends a service set identifier, a key and first token information of the first network to the first Internet of things device, instructs the first Internet of things device to join the first network, and requests the second server to bind the device information with the second account indicated by the first token information.

In the above embodiment, the first device subdivides the process of adding the first internet of things device into a plurality of links, and downloads the corresponding standard data from the first server when each link is executed. Therefore, if the first equipment interrupts adding the first Internet of things equipment in the middle, the first equipment does not need to download standard data related in the subsequent links, and invalid occupation of memory resources of the first equipment is reduced.

In some embodiments, the first data, the second data, the third data, the fourth data, and the fifth data in the first server are all plugins or executable scripts.

In some embodiments, after displaying the third interface, the method further comprises: the first device deletes the first data.

In the above embodiment, after the first device uses the second data, the third data, the fourth data and the fifth data, the first device may also delete the second data, the third data, the fourth data and the fifth data directly, so that the memory occupation is reduced, and the normal operation of the original firmware in the first device is not affected.

In a second aspect, an embodiment of the present application provides a device management method, applied to a first device, where the first device is communicatively connected to a first server, and the method includes: responding to a first operation of a user, and displaying a first interface, wherein the first interface is an Internet of things equipment discovery interface; during the display of the first interface, a first request is sent to a first server in response to received first hot spot information, wherein the first hot spot information is broadcast by first Internet of things equipment and comprises a first name corresponding to the first Internet of things equipment, and the first request comprises the first name and an identifier indicating an equipment discovery link; receiving first data sent by a first server, wherein the first data comprises a device discovery communication standard followed by first Internet of things equipment; operating the first data and sending a first discovery request to the first Internet of things equipment; after receiving the first response information, displaying a second interface, wherein the first response information is fed back by the first Internet of things equipment, and the first response information carries the equipment information of the first Internet of things equipment; the second interface comprises a first option control, and the first option control is used for displaying equipment information of the first Internet of things equipment; after detecting the operation of the user on the first option control, displaying a third interface, wherein the third interface comprises a first management control, and the first management control corresponds to the first Internet of things device and is used for triggering the sending of a control instruction to the first Internet of things device.

In some embodiments, after detecting the operation of the first option control by the user, in a scenario in which the first device logs in to the first account provided by the first server, the method further includes: logging in a second account provided by a second server, wherein the second server is a server corresponding to the first Internet of things equipment; and sending the second account to the first server, and indicating the first server and the second server to associate the first account with the second account, wherein after the first account is associated with the second account, the first account in the first server corresponds to the bound Internet of things equipment under the second account.

In some embodiments, after detecting the user operation of the first option control, the method further comprises: a third request is sent to the first server, wherein the third request comprises a first name and an identifier of an indication equipment network distribution link; receiving third data fed back by the first server, wherein the third data comprises equipment distribution network communication standards followed by the first Internet of things equipment; and running the third data, and sending the service set identification and the secret key of the first network to the first Internet of things device to instruct the first Internet of things device to join the first network.

In some embodiments, in a case where the first account and the second account have been associated in the first server, after detecting the operation of the first option control by the user, the method further includes: sending a fourth request to the first server, wherein the fourth request comprises a first name and an identifier indicating a binding link of the equipment; receiving fourth data fed back by the first server, wherein the fourth data comprises a first interface required to be called by the binding first Internet of things equipment; and running fourth data, and sending a first call request to a first interface of the second server through the first server, wherein the first call request comprises the second account and the equipment information of the first Internet of things equipment, and instructs the second server to bind the second account and the first Internet of things equipment.

In some embodiments, in a case where the first account and the second account have been associated in the first server, after detecting the operation of the first option control by the user, the method further includes: a third request is sent to the first server, wherein the third request comprises a first name and an identifier of an indication equipment network distribution link; receiving fifth data fed back by the first server, wherein the fifth data comprises equipment distribution network communication standards followed by the first Internet of things equipment; operating fifth data, and sending token request information to a second server through the first server, wherein the token request information comprises a second account; receiving first token information fed back by a second server through a first server, wherein the first token information corresponds to the second account; and sending a service set identifier, a secret key and first token information of a first network to the first Internet of things device, indicating the first Internet of things device to join the first network, and requesting the second server to bind the device information with a second account indicated by the first token information.

In some embodiments, after the displaying the third interface, the method further comprises: and deleting the first data.

In a third aspect, an embodiment of the present application provides a device management method, applied to a first server, where the first server is communicatively connected to a first device, and the method includes: receiving a first request sent by first equipment, wherein the first request comprises a first name and an identifier for indicating an equipment discovery link, the first name is information carried in first hot spot information monitored by the first equipment, and the first hot spot information is hot spot information broadcast by first Internet of things equipment; and responding to the first request, sending first data to the first device, wherein the first data comprises device discovery communication standards followed by the first Internet of things device, and indicating the first device to communicate with the first Internet of things device according to the device discovery standards carried in the first data.

In some embodiments, the method further comprises: receiving a third request sent by first equipment, wherein the third request comprises a first name and an identifier for indicating an equipment network distribution link; and responding to the third request, and sending third data to the first equipment, wherein the third data comprises equipment distribution network communication standards followed by the first Internet of things equipment, and the first equipment is indicated to communicate with the first Internet of things equipment according to the equipment distribution network standards carried in the third data.

In some embodiments, the method further comprises: receiving a fourth request sent by the first device, wherein the fourth request comprises a first name and an identifier for indicating a device binding link; and responding to the fourth request, and sending fourth data to the first equipment, wherein the fourth data comprises a first interface required to be called by the binding first Internet of things equipment, and the first equipment is indicated to bind the first Internet of things equipment with the corresponding second account by calling the first interface.

In a fourth aspect, an electronic device provided by an embodiment of the present application includes one or more processors and a memory; the memory is coupled to the processor, the memory for storing computer program code comprising computer instructions that, when executed by the one or more processors, operate to: responding to a first operation of a user, and displaying a first interface, wherein the first interface is an Internet of things equipment discovery interface; during the display of the first interface, a first request is sent to the first server in response to received first hot spot information, wherein the first hot spot information is hot spot information broadcasted by first internet of things equipment, the first hot spot information comprises a first name corresponding to the first internet of things equipment, and the first request comprises the first name and an identifier indicating an equipment discovery link; receiving first data sent by the first server, wherein the first data comprises a device discovery communication standard followed by the first Internet of things device; operating the first data and sending a first discovery request to the first Internet of things device; after receiving first response information, displaying a second interface, wherein the first response information is information fed back by the first Internet of things equipment, and the first response information carries equipment information of the first Internet of things equipment; the second interface comprises a first option control, and the first option control is used for displaying equipment information of the first Internet of things equipment; after detecting the operation of the user on the first option control, displaying a third interface, wherein the third interface comprises a first management control, and the first management control corresponds to the first Internet of things device and is used for triggering the sending of a control instruction to the first Internet of things device.

In some embodiments, in a scenario in which the first device logs in to a first account provided by the first server, the one or more processors are further configured to: logging in a second account provided by a second server, wherein the second server is a server corresponding to the first Internet of things device; and sending the second account to the first server, and indicating the first server and the second server to associate the first account with the second account, wherein after the first account is associated with the second account, the bound internet of things equipment under the second account corresponds to the first account in the first server.

In some embodiments, after detecting the user's operation of the first option control, the one or more processors are further to: sending a third request to the first server, wherein the third request comprises the first name and an identifier of an indication equipment network distribution link; receiving third data fed back by the first server, wherein the third data comprises equipment distribution network communication standards followed by the first Internet of things equipment; and running the third data, and sending a service set identifier and a secret key of a first network to the first Internet of things device to instruct the first Internet of things device to join the first network.

In some embodiments, where the first account and the second account have been associated in the first server, after detecting the user's operation of the first option control, the one or more processors are further configured to: sending a fourth request to the first server, wherein the fourth request comprises the first name and an identifier indicating a binding link of the equipment; receiving fourth data fed back by the first server, wherein the fourth data comprises a first interface which is required to be called by the first Internet of things equipment; and running the fourth data, and sending a first call request to the first interface of a second server through the first server, wherein the first call request comprises the second account and the equipment information of the first Internet of things equipment, and indicates the second server to bind the second account and the first Internet of things equipment.

In some embodiments, where the first account and the second account have been associated in the first server, after detecting the user's operation of the first option control, the one or more processors are further configured to: sending a third request to the first server, wherein the third request comprises the first name and an identifier of an indication equipment network distribution link; receiving fifth data fed back by the first server, wherein the fifth data comprises equipment distribution network communication standards followed by the first Internet of things equipment; operating the fifth data, and sending token request information to a second server through the first server, wherein the token request information comprises the second account; receiving first token information fed back by the second server through the first server, wherein the first token information corresponds to the second account; and sending a service set identifier, a secret key and first token information of a first network to the first Internet of things device, indicating the first Internet of things device to join the first network, and requesting the second server to bind the device information with a second account indicated by the first token information.

In some embodiments, after the displaying the third interface, the one or more processors are further to: and deleting the first data.

In a fifth aspect, an electronic device provided by an embodiment of the present application includes one or more processors and a memory; the memory is coupled to the processor, the memory for storing computer program code comprising computer instructions that, when executed by the one or more processors, operate to: receiving a first request sent by the first device, wherein the first request comprises a first name and an identifier for indicating a device discovery link, the first name is information carried in first hot spot information monitored by the first device, and the first hot spot information is hot spot information broadcasted by first Internet of things equipment; and responding to the first request, sending first data to the first device, wherein the first data comprises a device discovery communication standard followed by the first Internet of things device, and indicating the first device to communicate with the first Internet of things device according to the device discovery standard carried in the first data.

In some embodiments, the one or more processors are further to: receiving a third request sent by the first device, wherein the third request comprises the first name and an identifier indicating a network distribution link of the device; and responding to the third request, sending third data to the first equipment, wherein the third data comprises equipment distribution network communication standards followed by the first Internet of things equipment, and indicating the first equipment to communicate with the first Internet of things equipment according to the equipment distribution network standards carried in the third data.

In some embodiments, the one or more processors are further to: receiving a fourth request sent by the first device, wherein the fourth request comprises the first name and an identifier indicating a device binding link; and responding to the fourth request, sending fourth data to the first device, wherein the fourth data comprises a first interface which is required to be called by the first Internet of things device, and indicating the first device to bind the first Internet of things device with a corresponding second account by calling the first interface.

In a sixth aspect, embodiments of the present application provide a computer storage medium comprising computer instructions which, when run on an electronic device, cause the electronic device to perform the method of the second aspect, the third aspect and possible embodiments thereof.

In a seventh aspect, the present application provides a computer program product for causing an electronic device to carry out the method of the second, third and possible embodiments thereof.

It will be appreciated that the electronic device, the computer storage medium and the computer program product provided in the above aspects are all applicable to the corresponding methods provided above, and therefore, the advantages achieved by the electronic device, the computer storage medium and the computer program product may refer to the advantages in the corresponding methods provided above, and are not repeated herein.

Drawings

Fig. 1 is a schematic diagram of a system scenario provided in an embodiment of the present application;

FIG. 2 is one of exemplary diagrams of a scenario in which an IOT device is added in some embodiments;

FIG. 3 is a second exemplary diagram of a scenario in which an IOT device is added in some embodiments;

FIG. 4 is a third exemplary diagram of a scenario in which an IOT device is added in some embodiments;

FIG. 5 is a fourth example diagram of a scenario in which an IOT device is added in some embodiments;

FIG. 6 is an exemplary diagram of a scenario for adding an IOT device according to an embodiment of the present application;

Fig. 7 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application;

Fig. 8 is one of signaling interaction diagrams of a device management method according to an embodiment of the present application;

FIG. 9 is a schematic diagram of a display interface of an electronic device according to an embodiment of the present application;

FIG. 10 is a second schematic diagram of a display interface of an electronic device according to an embodiment of the present application;

FIG. 11 is a third schematic diagram of a display interface of an electronic device according to an embodiment of the present application;

FIG. 12 is a diagram illustrating a display interface of an electronic device according to an embodiment of the present application;

FIG. 13 is a second signaling diagram of a device management method according to an embodiment of the present application;

fig. 14 is a third signaling interaction diagram of a device management method according to an embodiment of the present application;

fig. 15 is a signaling interaction diagram of a device management method according to an embodiment of the present application;

Fig. 16 is a schematic diagram of a system-on-chip according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be combined

The technical solutions of the embodiments of the present application are clearly and completely described in the drawings, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The term "and/or" herein is an association relationship describing an associated object, and means that there may be three relationships, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. The symbol "/" herein indicates that the associated object is or is a relationship, e.g., A/B indicates A or B.

The terms "first" and "second" and the like in the description and in the claims are used for distinguishing between different objects and not for describing a particular sequential order of objects. In the description of the embodiments of the present application, unless otherwise specified, the meaning of "plurality" means two or more, for example, the meaning of a plurality of processing units means two or more, or the like; the plurality of elements means two or more elements and the like.

In embodiments of the 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 "e.g." in an embodiment should not be taken 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.

The implementation of the present embodiment will be described in detail below with reference to the accompanying drawings.

With the maturation of internet of things (internet of things, ioT) technology, various IoT devices have been widely used in various fields, which brings convenience to people's life and work. Taking smart home scenarios as an example, widely used IOT device types include audio and video devices (e.g., televisions, speakers, etc.), lighting systems, air conditioners, network devices, etc. In the smart home scene, with the increase of installed IOT devices, centralized management and control of various IOT devices are very important.

In some embodiments, a user may utilize a commonly used mobile terminal (e.g., a cell phone) to manage IOT devices in a smart home scenario. It will be appreciated that a mobile terminal for controlling IOT devices in a smart home scenario may also be referred to as a control terminal, which in practice is user-selected. That is, the control terminals corresponding to different smart home scenes may be different, and in addition, the same smart home scene may also correspond to a plurality of different control terminals, or the control terminals corresponding to different periods may also be different. In the following embodiments, the device management method provided by the embodiments of the present application is described by taking the control terminal as an example of a mobile phone.

Exemplary scenario, fig. 1, a user's home is equipped with a television, speakers, and projector. The television, the sound box and the projector all belong to the IOT device and have the capability of being added into a local area network, that is, the television, the sound box and the projector can perform data interaction with other devices (such as a mobile phone). Thus, the user can instruct the mobile phone to interact with the television, the sound box and the projector by operating the mobile phone, and bring the television, the sound box and the projector into the control range of the mobile phone.

Thus, the user can remotely control the television to turn on, turn off, adjust the volume, switch channels and the like through the mobile phone, can remotely control the loudspeaker to turn on, turn off, adjust the volume, switch channels and the like through the mobile phone, and can remotely control the projector to turn on, turn off, start projection, adjust the volume and the like through the mobile phone.

It will be appreciated that prior to the handset hosting the IOT device, the IOT device needs to be added to the handset's hosting scope. The above process may be referred to as adding IOT devices to the handset.

In some embodiments, the adding IOT device by the handset includes: device discovery, network configuration negotiation, device binding, and the like.

The device discovery means that the mobile phone detects the IOT device that needs to be added, and determines relevant information of the IOT device, such as a name, a manufacturer, a device identity, a model, and the like.

The negotiation of the distribution network refers to that the mobile phone assists the discovered IOT device to access to a specified local area network, so that the IOT device can interact data with the outside.

The above device binding refers to binding the IOT device with the mobile phone in the configured network, so that the mobile phone has the authority to control the IOT device.

Obviously, in any link, the mobile phone needs to perform data interaction with the IOT device, and in the interaction process, both sides need to follow the same rules and standards, for example, in the device discovery link, the communication interface needs to be called, and the transmitted message format and the like all belong to a part of the rules and standards.

However, since the manufacturer of the handset is different from the manufacturer of the IOT device, there is a difference in the rules and standards that the handset follows from the rules and standards that the IOT device follows. For example, in the device discovery link, the rule in the mobile phone indicates to send the probe message to the interface a that invokes the IOT device, but the rule in the IOT device indicates that the corresponding probe message can only be responded when the interface b is invoked. In addition, the above rules are written in Firmware (Firmware) of the mobile phone and the IOT device, and it is obvious that it is difficult for both parties to complete the addition of the device without modifying the Firmware of both the mobile phone and the IOT device.

In some embodiments, a manufacturer of the IOT device (abbreviated device vendor) may integrate a software development kit (software development kit, SDK) corresponding to the handset into firmware of the IOT device. The SDK corresponding to the mobile phone (called mobile phone SDK for short) comprises rules and standards for various data interaction between the mobile phone and the IOT equipment, and the mobile phone SDK is written and issued by a manufacturer of the mobile phone (called mobile phone manufacturer for short). After the firmware of the IOT device integrates the mobile phone SDK, the IOT device can be considered to be added to the IOT ecology corresponding to the mobile phone manufacturer, that is, the IOT device can support addition and management and control of the mobile phone. Of course, SDKs corresponding to different models or handsets from different manufacturers may also be different, so in order to support more types of handsets, multiple types of handsets SDKs need to be integrated in firmware of the IOT device, which also occupies large amount of storage resources of the IOT device.

Obviously, for equipment manufacturers, not only is the firmware of the IOT device time consuming and laborious to be modified, but also equipment which is sold and is not integrated with the mobile phone SDK cannot be considered. It will be appreciated that IOT devices that are sold and do not integrate the handset SDK cannot be recalled because they are sold, resulting in the inability to retrofit their firmware. Obviously, unilateral firmware modification by equipment manufacturers can lead users and IOT equipment to be controlled in the hands of mobile phone manufacturers, so that the commercial interests of the equipment manufacturers cannot be taken care of, and obviously, large-scale equipment manufacturers are unwilling to cooperate in this way.

In other embodiments, a device manufacturer may build a dedicated IOT server, referred to as a device IOT server. Wherein all products under the equipment factory commercial flag can access the equipment IOT server. In addition, after an application program (simply referred to as a device application) provided by a device manufacturer is installed, the mobile phone can also access the device IOT server, so that the mobile phone can perform data interaction with the device IOT server by enabling the device application, for example, registering or logging in a device service account corresponding to a user in the device IOT server through the device application. For another example, a user may bind a purchased IOT device from the device vendor under a device service account corresponding to the user by operating the device application.

Of course, the mobile phone manufacturer also builds a dedicated IOT server, which is called a mobile phone IOT server for short. The mobile phone can be configured with an application program corresponding to the mobile phone IOT server, such as an internet of things application, wherein the internet of things application can be a native application in the mobile phone or an application downloaded by the mobile phone in response to user instructions. In addition, the user can register or log in the corresponding mobile phone service account number in the mobile phone IOT server through the Internet of things application. In addition, the mobile phone IOT server and the equipment IOT server can conduct data interaction. It will be appreciated that the above-described internet of things application is one example of an application program in a cell phone that centrally manages IOT devices from different device vendors.

In some examples, the mobile phone may respond to the operation of the user on the internet of things application, and instruct the mobile phone IOT server and the device IOT server to associate the mobile phone service account corresponding to the user with the device service account, and the specific implementation process may refer to a related technology, for example, may complete the association between accounts according to a standard oauth2.0 protocol.

After the mobile phone service account is associated with the device service account, the mobile phone IOT server may obtain relevant information of the IOT device bound under the corresponding device service account from the device IOT server. Thus, after the mobile phone enables the Internet of things application and logs in the mobile phone service account corresponding to the user, the IOT equipment bound under the corresponding equipment service account can be displayed in an application interface of the Internet of things application. After that, the mobile phone can respond to the operation of the user in the application interface of the internet of things application, and send a control instruction to the IOT equipment through the mobile phone IOT server and the equipment IOT server, so that the remote control of the mobile phone on the IOT equipment is realized. Of course, the mobile phone can also directly start the device application, operate in the application interface of the device application, and remotely control the corresponding IOT device through the IOT server.

For example, as shown in fig. 2, a user purchases a television set for home, such as television 203 in fig. 2, where television 203 has the capability of performing ad hoc networking with other devices, and belongs to IOT devices. In order to bring the television 203 into the control range of the mobile phone, the user needs to install a device application corresponding to the television 203, such as a smart television application, in the mobile phone. After the smart tv application is installed, an application icon of the smart tv application may be included in the main interface 201 of the mobile phone. In this scenario, the mobile phone may discover the surrounding tv 203 through the smart tv application, provision the network to the tv, and instruct the tv manufacturer IOT server to bind the tv 203 under a device service account (e.g., called a tv service account) provided by the tv manufacturer server. Thus, after the mobile phone service account is associated with the television service account, the mobile phone IOT server may obtain the device bound under the television service account, that is, the related information of the television 203, from the IOT server of the television manufacturer. In this way, the mobile phone may display the application interface 204 provided by the internet of things application in response to the user's operation on the application icon 202, such as a click operation. The application interface 204 displays control controls corresponding to the television 203, such as a card 205. The card 205 contains information corresponding to the television 203, and the information includes information about the television 203, and also includes the current position of the television 203 and status information corresponding to the television 203 (i.e., whether the card is on-line or off-line).

In addition, the cell phone may also remotely control the television 203 in response to user operation of the card 205. In addition, the control controls may be displayed in a form of a floating window, an image, or the like, besides being displayed in a form of a control card, and the embodiment of the application is not particularly limited. In addition, the mobile phone can also directly enable the smart television application to control the television 203.

However, the IOT server of the television manufacturer can only assist the internet of things application to manage IOT products in the television factory commercial flag, and as the types of IOT devices purchased in the user's home are increased, the manufacturers from which the IOT devices come are different, so that the user needs to install a large number of application programs corresponding to the IOT server of the device in the mobile phone.

For example, as shown in fig. 3, in the case where the user purchases a sound box and a projector in addition to the television 203 for the IOT device purchased at home, if the sound box, the projector and the television come from different device manufacturers, the mobile phone needs to install a smart sound box application corresponding to the sound box and a projector application corresponding to the projector in addition to the smart television application. In addition, the mobile phone needs to enable different application programs (such as a smart television application, a smart sound box application and a projector application), bind different IOT devices (televisions and projector sound boxes) on different device service accounts, and then the internet of things application in the mobile phone interacts with each device IOT server through the mobile phone IOT server to associate the mobile phone service account with each device service account, so as to obtain the IOT devices bound under each device service account. Thus, as shown in fig. 3, the mobile phone may display the application interface 301 provided by the internet of things application in response to the user's operation on the application icon 202, such as a click operation. The application interface 301 includes not only the card 205, but also a card 302 corresponding to the sound box and a card 303 corresponding to the projector. The card 302 corresponding to the sound box also displays the information corresponding to the sound box, where the information includes the relevant information of the sound box, and also includes the current position of the sound box and the state information corresponding to the sound box (i.e., whether the sound box is on-line or off-line). Likewise, the projector-corresponding card 303 also displays projector-corresponding information including projector-related information, and also including the current position of the projector, and projector-corresponding status information (i.e., whether it is in an on-line state or an off-line state). Similarly, the mobile phone can control the corresponding IOT device according to the operation of the user on each card in the application interface 301.

Obviously, as IOT devices in home increase, manufacturers corresponding to IOT devices are diversified, and a large number of application programs, namely device applications corresponding to IOT servers of various devices, need to be installed on mobile phones. In this way, the in-home IOT devices can be brought into the regulatory range of the handset.

Obviously, in addition to binding IOT devices to device service accounts, the internet of things application has functions of various device applications, such as managing and controlling corresponding IOT devices. Obviously, the device application described above is somewhat redundant to the user after the IOT device has completed binding. In addition, before binding the IOT device, if there is no corresponding device application in the mobile phone, the user must also operate the mobile phone to download the corresponding device application, so that the man-machine interaction efficiency of receiving the IOT device into the mobile phone control range is low, and the storage resources of the excessive mobile phone are also occupied.

In other embodiments, the SDK provided by the IOT device, abbreviated as the device SDK, may be integrated in a program file of the internet of things application. The device SDK includes rules and standards to be followed for adding IOT devices. For example, after the integrated device SDK is applied to the internet of things of the mobile phone, the user can directly discover IOT devices existing around the mobile phone through the internet of things application. For another example, the device IOT server may be instructed by the internet of things application to authorize the mobile phone to register or log in a device service account corresponding to the user, and associate the device service account with the mobile phone service account. For another example, the internet of things application may be used to provide the IOT device with a network, so that the IOT device may access a corresponding IOT server. For another example, the IOT device may also respond to the indication of the internet of things application, access the IOT server of the device, and bind the IOT device with the device service account of the user, so that the IOT device bound under the device service account corresponding to the user may be shared under the mobile phone service account of the user through data interaction between the mobile phone IOT server and the device IOT server.

After that, the mobile phone can respond to the operation of the user in the application interface of the internet of things application, and send a control instruction to the IOT equipment through the mobile phone IOT server and the equipment IOT server, so that the remote control of the mobile phone on the IOT equipment is realized.

For example, as shown in fig. 4, in a scenario where a SDK corresponding to a television is integrated in a program file of an internet of things application, if a user newly purchases a television 203, a mobile phone may perform data interaction with a television 204 by using the SDK corresponding to the television, so as to complete tasks such as finding the television, authorizing the mobile phone to log into a television service account, configuring a network for the television, and binding the television with the television service account. After that, the handset may display the application interface 401 of the internet of things application in response to the user clicking on the application icon 202 of the internet of things application. The application interface 401 includes a card 402 corresponding to the television, where the card 402 is the same as the card 205 in fig. 2, and is used to display information corresponding to the television 203. In this way, the mobile phone can remotely control the television 203 through the mobile phone IOT server and the television vendor IOT server in response to the user's operation on the card 402.

However, the SDK corresponding to the television can only support the data interaction between the mobile phone and the television. If the mobile phone needs to support data interaction with more IOT devices, the SDKs of all devices need to be integrated in the program files of the internet of things application. With the increasing number of IOT devices, the more devices SDKs are integrated in the program files of the internet of things application. In addition, the SDK of the equipment in the program file, namely, the internet of things application in the mobile phone needs to be updated at any time, and frequent updating not only affects the normal use of the user, but also causes the continuous increase of the occupied storage space of the program file of the internet of things application. In addition, if only the IOT device supported by the mobile phone is used, whether the user purchases the IOT device or not, the internet of things application needs to include the SDK corresponding to the IOT device, which also causes the waste of storage space to a certain extent.

For example, as shown in fig. 5, in a scenario where the mobile phone supports data interaction with IOT devices such as a television, a projector, a sound box, and a fingerprint lock, the corresponding program file of the internet of things application is integrated with the SDK of the television, the SDK of the projector, the SDK of the sound box, and the SDK of the fingerprint lock. In this scenario, if the user purchases only the television, the projector, and the sound box at home and does not purchase the fingerprint lock, after the mobile phone adds the IOT device, the mobile phone responds to the user operation on the application icon 202, and the application interface 501 corresponding to the internet of things application can be displayed, where the application interface 501 includes control cards corresponding to the television, the projector, and the sound box, so that the mobile phone can control the corresponding IOT device according to the user operation on each control card. In addition, since the user does not purchase the fingerprint lock, the SDK corresponding to the fingerprint lock cannot be started for a while. However, the SDK of the fingerprint lock always occupies the storage space of the mobile phone, which forms a waste of resources and affects the performance of the mobile phone.

In order to improve the problems, the embodiment of the application provides a device management method, which ensures the efficiency of adding and controlling the IOT device by the mobile phone on the premise of not modifying the firmware of the IOT device and the program files of the application programs in the mobile phone.

Illustratively, as shown in fig. 6, a cell phone IOT server (first server) may interact with data from various device IOT servers. Plug-in or rule configuration files provided by different equipment manufacturers are configured in the mobile phone IOT server. The plug-in is a program package, and the program package contains standards and rules required to be followed by data interaction with the IOT device. The mobile phone runs the program package, so that the device discovery, authorized login, device network allocation, device binding and the like of the IOT device can be realized. The rule configuration file is an executable script file, and can be driven to realize device discovery, authorized login, device network allocation, device binding and the like for the IOT device. Of course, the plug-in or rule configuration file for each device vendor applies only to IOT devices during that device vendor.

In some examples, plug-ins provided by various device vendors may be configured in the cell phone IOT server. In other embodiments, the rule configuration files provided by each device vendor may be configured in the cell phone IOT server. Both modes can be adopted, in the following embodiment, the method provided by the application is described by taking the scene of configuring the plug-in the mobile phone IOT server as an example, and of course, the scene of configuring the rule configuration file in the mobile phone IOT server is the same.

As shown in fig. 6, when a mobile phone (first device) needs to add a television to a control range, the mobile phone may obtain a plug-in corresponding to the television from an IOT server of the mobile phone through an internet of things application, and then, the mobile phone uses the obtained plug-in to perform device discovery, authorized login, network allocation, device binding and the like for the television. Similarly, when a mobile phone needs to add a sound box to a control range, the mobile phone can acquire plug-in components corresponding to the sound box from the mobile phone IOT server through the Internet of things application, and then the mobile phone uses the acquired plug-in components to perform equipment discovery, authorized login, network distribution, equipment binding and the like on the sound box. When the mobile phone needs to add the projector to the control range, the mobile phone can acquire the plug-in corresponding to the projector from the mobile phone IOT server through the Internet of things application, and then the mobile phone uses the acquired plug-in to perform equipment discovery, authorized login, network distribution, equipment binding and the like on the projector.

Thus, as shown in fig. 6, in response to the operation of the application icon 202 of the internet of things application by the user, the mobile phone may display an application interface 601 of the internet of things application, where control cards corresponding to the television, the sound box and the projector are displayed in the application interface 601, so that the mobile phone may control corresponding IOT devices according to the operation of the user on each control card. Therefore, under the cooperation of the mobile phone IOT server, the mobile phone has the capability of supporting the addition and the management of various IOT equipment, and meanwhile, the firmware of the IOT equipment does not need to be modified. The mobile phone can download necessary plug-ins or rule configuration files according to actual conditions, and meanwhile, the plug-ins and rule configuration files do not influence the normal starting of the internet of things application even if being cleared. Compared with the SDK corresponding to the integrated device in the program file of the Internet of things application, the volume of the program file of the Internet of things application is effectively reduced, the program file of the Internet of things application in the mobile phone does not need to be frequently updated, and unnecessary storage space is not occupied.

In some embodiments, the above-described methods may be applied to an electronic device. The electronic device in the embodiment of the present application may be a mobile phone, a tablet computer, a desktop (desktop computer), a handheld computer, a notebook (laptop computer), an ultra-mobile personal computer, a UMPC, a netbook, a personal digital assistant (personal DIGITAL ASSISTANT, PDA), an augmented reality (augmented reality, AR) \virtual reality (VR) device, or the like, in which the mail application may be installed, and the embodiment of the present application does not particularly limit the specific form of the electronic device. In addition, the operating system of the electronic device may be an Android (Android), an IOS (input/output) system or other operating systems, and the embodiment of the application does not limit the type of the operating system of the electronic device.

The following describes in detail the implementation of the embodiment of the present application with reference to the drawings. Fig. 7 is a schematic structural diagram of an electronic device 100 according to an embodiment of the application. As shown in fig. 7, the electronic device 100 may include: processor 110, external memory interface 120, internal memory 121, universal serial bus (universal serial bus, USB) interface 130, charge management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headset interface 170D, sensor module 180, keys 190, motor 191, indicator 192, camera 193, display 194, and subscriber identity module (subscriber identification module, SIM) card interface 195, etc.

The sensor module 180 may include a pressure sensor, a gyroscope sensor, a barometric sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

It is to be understood that the structure illustrated in the present embodiment does not constitute a specific limitation on the electronic apparatus 100. In other embodiments, electronic device 100 may include more or fewer components than shown, 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.

The processor 110 may include one or more processing units, such as: the processor 110 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 memory, a video codec, a digital signal processor (DIGITAL SIGNAL processor, DSP), a baseband processor, and/or a neural Network Processor (NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller may be a neural hub and command center of the electronic device 100. 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 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it may be called directly from memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 110 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 connection relationship between the modules illustrated in this embodiment is only illustrative, and does not limit the structure of the electronic device 100. In other embodiments, the electronic device 100 may also employ different interfaces in the above embodiments, or a combination of interfaces.

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

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a Liquid Crystal Display (LCD) CRYSTAL DISPLAY, an organic light-emitting diode (OLED), an active-matrix organic LIGHT EMITTING diode (AMOLED), a flexible light-emitting diode (FLED), miniled, microLed, micro-oLed, a quantum dot LIGHT EMITTING diode (QLED), or the like.

The electronic device 100 may implement photographing functions through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The ISP is used to process data fed back by the camera 193. 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 electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing, so that the electrical signal 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 193.

The camera 193 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, electronic device 100 may include N cameras 193, 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 electronic device 100 selects a frequency bin, the digital signal processor is used to fourier transform the frequency bin energy, or the like.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of 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 awareness of the electronic device 100 may be implemented through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, etc.

In the following, in conjunction with the accompanying drawings, the implementation details of the device management method provided by the application are described by taking an example that the electronic device is a mobile phone.

In some embodiments, before the IOT device is managed, the handset needs to add the IOT device to the management scope, which may also be referred to as acquiring the management authority of the IOT device. For example, adding IOT devices may be standardized to multiple business processes, such as a device discovery process, an authorized login process, a device networking process, and a device binding process.

In some embodiments, as shown in fig. 8, the device discovery process includes the following steps:

S100, IOT device 1 broadcasts corresponding hotspot information.

In some embodiments, it may be desirable to power on IOT device 1 and remain discoverable until the user discovers IOT device 1 using a cell phone. It will be appreciated that, in the wireless access node (AP) mode, the IOT device 1 is an access point of a hotspot network, and may broadcast hotspot information outwards. The hotspot information carries a hotspot identifier, for example, the hotspot identifier may be a hotspot network name corresponding to the hotspot network. In some embodiments, the hotspot identifier carried in the hotspot information corresponding to the IOT device 1 may be model information of the IOT device, where the model information of the IOT device may indicate a device vendor corresponding to the IOT device 1. In this way, the external device (including the mobile phone) not only can discover the IOT device 1 according to the hotspot information sent by the IOT device 1, but also can determine the device manufacturer of the IOT device 1.

In some examples, IOT device 1 may automatically enter AP mode after first powering up, powering up. In the AP mode, IOT device 1 will continuously broadcast hotspot information to the outside while IOT device 1 is in a discoverable state.

In other examples, IOT device 1 is configured with a key to initiate AP mode. After detecting that the user clicks a key to activate AP mode, IOT device 1 may enable AP mode to enable IOT device 1 to be discovered.

S101, the mobile phone detects operation of the user to instruct the adding device.

The mobile phone runs an internet of things application, the internet of things application is a client provided by the mobile phone IOT server, and after the mobile phone runs the internet of things application, data interaction can be performed between the internet of things application and the mobile phone IOT server. Of course, in other embodiments, the application may also be a smart life application, a smart home application, and the like.

In some embodiments, the mobile phone may detect an operation made by the user in the mobile phone display during the application interface of the mobile phone foreground display internet of things application. For example, during the display of the application interface 601, the user makes an operation on the display screen of the cellular phone indicating to add a device.

As shown in fig. 9, during the display of the application interface 601, the handset displays a shortcut window 902 in response to a user operation of the control 901. Controls indicating different business functions, such as adding device controls, creating scene controls, and sharing device controls, are included in the shortcut window 902. In this scenario, the handset may switch to display the device search interface 1001 (first interface) shown in fig. 10 in response to the user's addition of the device control, so that the handset may initiate the flow of adding the device. That is, the indication made by the user displays the shortcut window 902 and the operation of selecting the add device control may be referred to as an operation of indicating the add device. In addition, the operation of instructing to display the first interface may be referred to as a first operation.

In some embodiments, there is no necessary sequence between S100 and S101, but after step S101, if S100 is not performed, that is, IOT device 1 does not broadcast hotspot information, then the handset cannot discover IOT device 1.

S102, the mobile phone monitors hot spot information sent by other devices.

In some embodiments, after receiving an operation indicating to add a device, the handset may not only display the device search interface 1001 in response to the operation, but also listen for information broadcast around during the display of the device search interface 1001. By the method, the mobile phone can find out the hot spot network existing around. For example, when the mobile phone monitors a piece of hot spot information, it can be determined that the hot spot network indicated by the hot spot information is near the mobile phone, that is, the wireless access port of the hot spot network is closer to the mobile phone. If the piece of hotspot information comes from the IOT device, the mobile phone can also find out that the IOT device exists around according to the hotspot information.

For example, keywords related to different device manufacturers may be preset in the mobile phone, so that when the hotspot identifier for monitoring the hotspot information includes the keywords related to the device manufacturer, it may be determined that the hotspot information comes from the IOT device, and in addition, the different device manufacturers may be device manufacturers that have access to the IOT ecology. For example, when the mobile phone receives the hotspot information 1 from the television, the hotspot identifier of the hotspot information 1 contains the same content as the keyword of the television manufacturer, it can be determined that the hotspot information 1 is the hotspot information from the IOT device. For another example, the mobile phone receives the hotspot information 2 from the router, where the hotspot information 2 is only a user-defined network noun (e.g., home network), and it may be determined that the hotspot information 2 is not the hotspot information from the IOT device.

In other embodiments, the mobile phone may further record the monitored hotspot information to obtain a list including the hotspot information, which is abbreviated as a hotspot list. The hotspot list may be emptied after the end of the monitoring of hotspot information.

S103, after monitoring the hot spot information from the IOT equipment 1, sending query information 1 to the mobile phone IOT server, wherein the query information 1 comprises hot spot identification in the hot spot information.

In some embodiments, when the mobile phone determines that the monitored hotspot information is from the IOT device, the mobile phone may send a corresponding query message to the IOT server of the mobile phone. The corresponding query information carries hotspot information corresponding to the IOT device, that is, carries model information of the IOT device, so that a plug-in corresponding to the IOT device can be queried from a mobile phone IOT server through the query information.

In some embodiments, the queried plugin may be a total plugin for multiple business links such as device discovery, login authorization, device distribution network, and device binding for the IOT device.

In other embodiments, the queried plug-in may be a plug-in that performs the current traffic link (i.e., device discovery link) only for the IOT device. Thus, the query information may further include an identifier indicating the current service link, for example, an identifier indicating the device discovery link. Thus, the transmitted query information is the query information related to the IOT equipment, and invalid query is avoided.

Taking a scenario in which hotspot information (first hotspot information) sent by IOT device 1 (first internet of things device) is monitored by a mobile phone as an example, after the mobile phone determines that the hotspot information is from one IOT device, the mobile phone may send query information 1 (first request) corresponding to IOT device 1 to the mobile phone IOT server, where query information 1 may include a hotspot identifier (first name) carried by the hotspot information, that is, a device model. In other possible examples, the query information 1 may also include an identification indicating a device discovery link. In the following embodiments, implementation details of the embodiments of the present application will be described by taking the example that the hotspot information corresponding to the IOT device 1 is received and the query information 1 is sent to the IOT server of the mobile phone.

In other embodiments, after initiating monitoring the hotspot information, the handset may record the monitored hotspot information. And when the hot spot information is monitored to have the same hot spot identification as the recorded hot spot information, not repeatedly recording. In this scenario, once a piece of hotspot information is recorded by the mobile phone, a piece of corresponding query information is sent to the IOT server of the mobile phone. The query information may also carry a hotspot identifier corresponding to the hotspot information. Of course, the query information may also include an identification indicating the device discovery link. Therefore, after the mobile phone monitors the hot spot information, the mobile phone does not need to judge whether the hot spot information comes from the IOT equipment or not, and the mobile phone also does not need to preset keywords corresponding to each equipment manufacturer.

S104, the mobile phone IOT server responds to the query information 1 to determine the plugin 1 corresponding to the IOT equipment 1.

In some embodiments, the IOT server of the mobile phone may parse the hotspot identification from the query information 1, and then identify which equipment manufacturer the hotspot identification matches, for example, the hotspot identification is the same as the equipment model of the product under the television manufacturer commercial flag, and determine that the hotspot identification matches the television manufacturer. For another example, the hotspot identification may conform to a naming convention for the device under television manufacturer commercial flag, and it may be determined that the hotspot identification matches the television manufacturer. The plug-in provided by the device vendor is then determined to be plug-in 1.

In some embodiments, if the query information 1 carries an identifier indicating a device discovery link, the determined plug-in 1 may be a plug-in applicable to the device discovery link, which may be referred to as first data. If the query information 1 does not carry the identifier indicating the discovery link of the device, the determined plugin 1 is the total plugin for all the service links.

In other embodiments, if there is no device vendor matching the hotspot identification, the process ends, which means that the AP corresponding to the hotspot identification does not belong to the IOT device, or the IOT ecology corresponding to the handset does not support the IOT device yet.

In addition, the device search interface 1001 further includes a control for indicating the scan add device and a control for manually inputting device information, if the mobile phone obtains the device information of the IOT device 1 in response to selecting the control for scanning add device or selecting the control for manually inputting device information, the mobile phone can directly use the device information to query the corresponding plug-in 1 from the IOT server of the mobile phone, which is the same as the foregoing embodiment, and the principle is not repeated here.

S105, the mobile phone IOT server sends the plug-in 1 to the mobile phone.

In some scenarios, the IOT server of the mobile phone may send multiple plug-ins to the mobile phone at the same time, where the multiple plug-ins are applicable to IOT devices of different models, and the multiple plug-ins may include plug-ins of IOT device 1. For example, the same equipment manufacturer provides different plug-ins for equipment of different models, and then a plurality of different plug-ins can be queried from the mobile phone IOT server according to the matched equipment manufacturer. For another example, when the hotspot identifier is not a complete device model, a plurality of device manufacturers matching the hotspot identifier may be queried, or a plurality of plugins may be queried from the mobile phone IOT server. For another example, when naming rules of multiple device manufacturers are close, multiple matching device manufacturers are determined, and multiple plug-ins 1 are also obtained.

S106, the mobile phone sends a device discovery instruction to the IOT device 1 based on the obtained plug-in 1.

In some embodiments, when plug-in 1 matches IOT device 1, the handset may run plug-in 1, send a device discovery instruction (first discovery request) to IOT device 1, to which IOT device 1 may respond. When the plug-in 1 is not matched with the IOT device 1, the mobile phone runs the plug-in 1, and can also send a device discovery instruction to the IOT device 1, but the IOT device 1 does not respond.

Wherein, the plug-in 1 matches with the IOT device 1, which means that the communication standard contained in the plug-in 1 is consistent with the communication standard followed by the IOT device 1. Thus, after the mobile phone runs the plug-in 1, the sent device discovery command accords with the standard of the IOT device 1, and the communication interface pointed by the device discovery command is also a communication interface for device discovery in the IOT device 1.

Conversely, a card 1 does not match IOT device 1, meaning that the communication standard used in card 1 is different from the communication standard followed by IOT device 1.

In some scenarios, when receiving multiple plugins 1 at the same time, the mobile phone may run each plugin 1 in turn, and send a corresponding device discovery instruction to the IOT device 1.

In addition, before S106, after S105, the mobile phone may access the hotspot network corresponding to the IOT device 1 according to the hotspot information corresponding to the IOT device 1, so as to facilitate the interaction between the mobile phone and the IOT device.

S107, IOT device 1 transmits device discovery response information.

If the plug-in 1 is matched with the IOT device 1, the IOT device 1 can accept and identify a device discovery instruction sent by the plug-in 1 when the mobile phone runs and feed back corresponding device discovery response information (first response information). In this way, the mobile phone carries the device information corresponding to the IOT device 1 according to the device discovery response information fed back by the IOT device. If the handset runs a plug-in that does not match IOT device 1, IOT device 1 does not respond.

As one implementation, the following program data may be used to implement S106 and S107 described above:

apName＝context.getVariable(“apName”)

conn＝network.connect(apName)

DeviceInfo devInfo＝conn.send(“getDeviceDetailInfo”)；

return devInfo。

Wherein apName refers to a hotspot identifier, network connection (apName) refers to a hotspot network corresponding to the connection hotspot identifier, and getDeviceDetailInfo refers to a device discovery instruction. Return devInfo above refers to IOT device 1 returning device information.

S108, the mobile phone displays the device information corresponding to the IOT device 1.

In some embodiments, after receiving the device discovery response information, determining that the plugin 1 is a plugin for the IOT device 1, the device information corresponding to the plugin 1 may be determined to be the device information corresponding to the IOT device 1, and the device information may be displayed in the discovery list interface. In this way, the user may choose whether to add the IOT device 1 to the regulatory scope of the handset.

For example, during device scanning, that is, when the cell phone displays the device search interface 1001, the IOT device 1 that determines the device information includes an a-air conditioner and a sweeping robot, as shown in fig. 11, a discovery list interface (e.g., interface 1101 or referred to as a second interface) is displayed, and the interface 1101 includes an add card for displaying the device information of the a-air conditioner and an add card for displaying the device information of the sweeping robot. Wherein an add-on card for displaying device information of IOT device 1 may be referred to as a first option control.

In addition, other IOT devices are added similarly, and the mobile phone can also respond to the second operation of the user to display the first interface. And during the display of the first interface, the mobile phone responds to the received second hot spot information, and sends a second request to the mobile phone IOT server, wherein the second hot spot information is the hot spot information broadcast by the second Internet of things device, the second hot spot information comprises a hot spot identifier (namely, a second name) corresponding to the second Internet of things device, and the second request comprises the second name and an identifier indicating a device discovery link. The mobile phone IOT server responds to the second request and sends second data to the first device, wherein the second data comprises a device discovery communication standard followed by the second internet-enabled device; the mobile phone runs second data and sends a second discovery request to the second internet-connected device; after the mobile phone receives second response information, a discovery list interface (also called a fourth interface) is displayed, wherein the second response information is information fed back by the second physical equipment, and the second response information carries equipment information of the second physical equipment; the fourth interface includes a second option control for displaying device information of the second physical connection device.

In some embodiments, the handset may proceed to the next business segment, i.e., the authorized login segment. In some embodiments, the authorized login procedure may guide the user to login to the vendor account of the device (without the guide registration of the account) according to the standard oauth2.0 protocol, and after the oauth2.0 login is successful, the user establishes a binding relationship with the account systems of the two parties. Illustratively, as shown in fig. 13, the above-mentioned authorized login procedure may include the following steps:

s201, the mobile phone receives the operation of selecting the IOT equipment 1 from the user indication.

In some embodiments, the operation of selecting IOT device 1 may be a selection operation of adding a card to any IOT device, for example, clicking on the add card, during display of the discovery list interface by the mobile phone. For example, as shown in fig. 12, the mobile phone may switch to display an add waiting interface (e.g., interface 1201) in response to a user selecting an add card corresponding to an a air conditioner in the interface 1101.

S202, the mobile phone sends a device service account login/registration request to the device IOT server.

In some embodiments, the mobile phone may send a device service account login/registration request to an IOT server corresponding to IOT device 1, where the IOT server corresponding to IOT device 1 may also be referred to as a second server.

S203, the equipment IOT server sends a data packet corresponding to the account login/registration interface to the mobile phone.

In some embodiments, the account data package may be interface data written in fifth generation internet hypertext markup language (HTML).

S204, the mobile phone displays an account login/registration interface.

In some embodiments, the mobile phone may draw the rendering account login/registration interface based on the received data packet. The account login/registration interface may provide a service to log in to a device service account, and may also provide a service to register a device service account. When the mobile phone detects that the user selects the service of registering the equipment service account, the mobile phone can receive application information (such as user identity information, an account to be applied, an authentication password and the like) input by the user, then the application information is sent to the equipment IOT server, and when the equipment IOT server determines that the application information passes the audit, the application of the equipment service account is completed, and specific reference to related technologies is omitted herein. In the following embodiments, the user will mainly take the example of selecting the device service account login service.

S205, the mobile phone receives the device service account 1 and the authentication password input by the user.

Wherein device service account 1 may be referred to as a second account.

S206, the mobile phone sends the device service account 1 and the authentication password to the device IOT server.

S207, the equipment IOT server sends a login success notification to the mobile phone.

In some embodiments, the device IOT server performs login authentication based on the device service account 1 and the authentication password. And under the condition that the equipment service account 1 and the authentication password pass authentication, a login success notification is sent to the mobile phone.

S208, the mobile phone sends the equipment service account number 1 to the mobile phone IOT server.

In some embodiments, the mobile phone sends a device service account 1 to the mobile phone IOT server in response to the login success notification, instructing the mobile phone IOT server to associate the mobile phone service account with the device service account 1. The mobile phone service account is also called a first account.

S209, the mobile phone IOT server instructs the equipment IOT server to associate the equipment service account 1 with the mobile phone service account.

Thus, after the login authorization link is completed, the device distribution network and the device binding can be performed. In some embodiments, as shown in fig. 14, the process of the above device configuration network and device binding is as follows:

s301, the mobile phone sends query information 2 to the mobile phone IOT server, wherein the query information 2 comprises a hot spot identifier and an identifier for indicating equipment distribution network.

In some embodiments, the hotspot identifier is a hotspot identifier carried by the hotspot information sent by the IOT device 1 and is the same as the hotspot identifier carried in the query information 1. This query information 2 may also be referred to as a third request. The indication device network allocation identifier is used for indicating and inquiring a plug-in unit applicable to network allocation links for the IOT device 1.

S302, the mobile phone IOT server responds to the query information 2 to determine the plugin 2 corresponding to the IOT equipment 1.

In some embodiments, the implementation details of S302 may refer to S104 in the foregoing embodiments, which is not described herein.

S303, the mobile phone IOT server sends the plug-in unit 2 to the mobile phone.

S304, after the plug-in 2 is operated, the mobile phone instructs the mobile phone IOT server to send token request information to the equipment IOT server.

In some embodiments, after the mobile phone runs the plug-in 2, it may trigger sending a trigger message to the mobile phone IOT server, where the trigger message may include the mobile phone service account currently logged in by the mobile phone and an identifier indicating that the user token is acquired.

S305, the mobile phone IOT server sends token request information 2 to the equipment IOT server.

In some embodiments, the mobile IOT server may query the corresponding device service account of the mobile phone, that is, the device service account associated with the mobile phone service account currently logged in to the mobile phone, such as device service account 1, in response to the trigger information. And then, sending token request information carrying the device service account 1 to the device IOT server.

S306, the equipment IOT server sends a user token 1 to the mobile phone IOT server, and the user token 1 corresponds to the user service account 1.

In some embodiments, each registered device service account in the device IOT server corresponds to a user token that indicates the owner identity of the device service account. That is, the corresponding registered device service account 1 may correspond to the user token 1 (also referred to as first token information). Thus, when the device IOT server receives the token request information carrying the user service account 1, the device IOT server may feed back the user token 1 corresponding to the user service account 1 to the mobile phone IOT server.

S307, the mobile phone IOT server sends the user token 1 to the mobile phone.

After the handset IOT server obtains the user token 1, it may be forwarded to the handset.

And S308, the mobile phone sends the SSID of the appointed wireless network, the corresponding secret key and the user token 1 to the IOT equipment 1 according to the obtained plug-in unit 2.

In some embodiments, the designated wireless network (first network) may be a wireless local area network established by a router to which the handset is currently accessing. Thus, after the mobile phone runs the plug-in 2, the SSID and the key corresponding to the router can be obtained. After obtaining the SSID and the secret key, the mobile phone accesses a hotspot network corresponding to the IOT device 1 according to the hotspot information, and sends the SSID, the corresponding secret key and the user token 1 to the IOT device 1.

In other embodiments, the designated wireless network may also be a wireless local area network established by a user-selected router. For example, after the handset runs plug-in 2, a distribution network interface may be displayed that may direct the user to enter a service set identification (SERVICE SET IDENTIFIER, SSID) and corresponding key for the specified wireless network. Thus, after receiving the SSID and the corresponding key input by the user, the mobile phone joins the hotspot network corresponding to the IOT device 1 according to the hotspot information, and then sends the SSID of the designated wireless network, the corresponding key and the user token 1 to the IOT device 1.

As an implementation, the corresponding plug-in 2 may include the following program data:

apName＝context.getVariable(“apName”)

conn＝network.connect(apName)

conn.send ("networdEncrypyNegotiate")// secure encryption channel negotiation

Conn.send ("wifiInfo", ssid, pwd); transmission ssid and password

Conn.send ("userInfo", acessToken)// transmit user token information.

S309, the IOT equipment 1 joins the appointed wireless network according to the SSID and the corresponding secret key.

S310, the IOT equipment 1 sends a successful notification of network access to the mobile phone.

In some embodiments, the mobile phone receives the successful notification of network access and can switch to the wireless local area network established by the original router.

S311, IOT device 1 sends user token 1 and device information to the device IOT server.

In some embodiments, IOT device 1 may interact with a device IOT server via a designated wireless network after accessing the network, such that IOT device 1 transmits user token 1 and device information to the device IOT server.

S312, the device IOT server binds the IOT device 1 indicated by the device information with the user service account 1 according to the user token 1.

It can be understood that the above device information may uniquely indicate the IOT device 1, and meanwhile, the user token 1 is associated with the user service account 1, and the device IOT server may bind the IOT device 1 to the user service account 1 according to the received device information and the user token 1, so as to complete the addition process of the entire IOT device 1.

In some possible embodiments, if the plug-in 1 obtained in S105 is a total plug-in applicable to multiple service links such as device discovery, login authorization, device configuration network, and device binding, the method may not include S301 to S303.

In other possible embodiments, if the running plug-in 2 does not trigger sending the trigger information to the mobile phone IOT server, the method may not include S304-S307, S311 and S312. Wherein, the plug-in 2 that does not instruct to send the trigger information to the IOT server of the mobile phone may be referred to as third data. The plug-in 2 that instructs to send trigger information to the cell phone IOT server may be referred to as fifth data.

In addition, the data transmitted in S308 does not contain a user token. But after the equipment distribution network is completed, the equipment binding link is independently carried out. As shown in fig. 15, the above device binding procedure includes the following steps:

S401, the mobile phone sends query information 3 to the mobile phone IOT server, wherein the query information 3 comprises a hot spot identifier and an identifier indicating equipment binding.

In some embodiments, the hotspot identifier is a hotspot identifier carried by the hotspot information sent by the IOT device 1 and is the same as the hotspot identifier carried in the query information 1. The identifier indicating the device binding is used for indicating to query the plug-in unit applicable to the device binding link aiming at the IOT device 1 device.

S402, the mobile phone IOT server responds to the query information 3 to determine the plugin 3 corresponding to the IOT equipment 1.

In some embodiments, the query information 3 may also be referred to as a fourth request. The implementation details of S402 may refer to S104 in the foregoing embodiments, and are not described herein. The query 3 also includes a first name and an identifier indicating a binding link of the device. The plug-in 3 may also be referred to as fourth data, which contains a first interface to be invoked for binding the first internet of things device.

S403, the mobile phone IOT server sends the plug-in 3 to the mobile phone.

S404, after the plug-in 3 is operated, the mobile phone sends binding information to the mobile phone IOT server, and the binding information carries equipment information corresponding to the IOT equipment 1.

In some embodiments, the mobile IOT server may query a mobile service account currently logged in by the mobile in response to binding information sent by the mobile. The device service account associated with the handset service account, i.e., device service account 1, is then queried.

S405, the mobile phone IOT server sends binding call information to the device IOT server, wherein the binding call information carries device information and a device service account number 1.

In some embodiments, the binding call information described above may be referred to as a first call request.

S406, the device IOT server binds the IOT device 1 indicated by the device information with the user service account 1.

As an implementation, the above-mentioned insert 3 may be: iotatplatformproxy.httpresettemplate ("deviceBindInterface", params).

S407, the equipment IOT server sends a binding success notification to the mobile phone IOT server.

S408, the mobile phone IOT server sends a binding success notification to the mobile phone.

After IOT device 1 is bound to device service account number 1, IOT device 1 may be shared under the user's mobile phone service account number, so that the application interface 601 (also referred to as a third interface) of the mobile phone in the internet of things application may include a control card (such as referred to as a first management control) corresponding to IOT device 1, and thus, during enabling the internet of things application by the mobile phone, IOT device 1 may also be remotely controlled by a mobile phone IOT server and a device IOT server. In addition, after the IOT device 1 is added, the mobile phone can also clear all plug-ins corresponding to the IOT device 1, so that occupation of memory resources of the mobile phone is reduced. In other embodiments, the rule configuration file is also adopted, and the description thereof will not be repeated.

And similarly, after the mobile phone detects the operation of the user on the second option control indicating the second internet of things device, displaying a third interface again, wherein a second management control is newly added in the third interface, the second management control corresponds to the second internet of things device and is used for triggering the sending of a control instruction to the second internet of things device, and the second internet of things device and the first internet of things device come from different manufacturers.

The embodiment of the application also provides electronic equipment, which can comprise: a memory and one or more processors. The memory is coupled to the processor. The memory is for storing computer program code, the computer program code comprising computer instructions. The computer instructions, when executed by the processor, cause the electronic device to perform the steps performed by the handset in the embodiments described above. Of course, the electronic device includes, but is not limited to, the memory and the one or more processors described above.

The embodiment of the application also provides a chip system which can be applied to the terminal equipment in the embodiment. As shown in fig. 16, the system-on-chip includes at least one processor 2201 and at least one interface circuit 2202. The processor 2201 may be a processor in an electronic device as described above. The processor 2201 and the interface circuit 2202 may be interconnected by wires. The processor 2201 may receive and execute computer instructions from the memory of the electronic device described above through the interface circuit 2202. The computer instructions, when executed by the processor 2201, cause the electronic device to perform the steps performed by the handset in the embodiments described above. Of course, the system-on-chip may also include other discrete devices, which are not particularly limited in accordance with embodiments of the present application.

In some embodiments, it will be clearly understood by those skilled in the art from the foregoing description of the embodiments, for convenience and brevity of description, only the division of the above functional modules is illustrated, and in practical application, the above functional allocation may be implemented by different functional modules, that is, the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above. The specific working processes of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which are not described herein.

The functional units in the embodiments 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 computer 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 computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: flash memory, removable hard disk, read-only memory, random access memory, magnetic or optical disk, and the like.

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

Claims

1. A device management method applied to a first system including a first device and a first server, the method comprising:

the first equipment responds to a first operation of a user and displays a first interface, wherein the first interface is an Internet of things equipment discovery interface;

During the display of the first interface, the first device responds to the received first hot spot information and sends a first request to the first server, wherein the first hot spot information is hot spot information broadcasted by first internet of things equipment, the first hot spot information comprises a first name corresponding to the first internet of things equipment, and the first request comprises the first name and an identifier indicating a discovery link of the equipment;

the first server responds to the first request and sends first data to the first device, wherein the first data comprises a device discovery communication standard followed by the first Internet of things device;

the first device runs the first data and sends a first discovery request to the first Internet of things device;

After the first equipment receives first response information, displaying a second interface, wherein the first response information is information fed back by the first Internet of things equipment, and the first response information carries equipment information of the first Internet of things equipment; the second interface comprises a first option control, and the first option control is used for displaying equipment information of the first Internet of things equipment;

After the first device detects the operation of the user on the first option control, the first device sends a third request to the first server, wherein the third request comprises the first name and an identifier of an indication device network link, and the identifier of the indication device network link is used for indicating and inquiring a device network communication standard for the first device network link;

The first server responds to the third request and sends third data to the first device, wherein the third data comprises a device distribution network communication standard followed by the first Internet of things device;

The first device runs the third data, and sends a service set identifier and a secret key of a first network to the first Internet of things device to instruct the first Internet of things device to join the first network;

And displaying a third interface, wherein the third interface comprises a first management control, and the first management control corresponds to the first Internet of things device and is used for triggering the first Internet of things device to send a control instruction.

2. The method of claim 1, wherein after the displaying the third interface, the method further comprises:

the first device responds to a second operation of a user and displays the first interface;

during the display of the first interface, the first device responds to the received second hot spot information, and sends a second request to the first server, wherein the second hot spot information is hot spot information broadcast by a second piece of connected equipment, the second hot spot information comprises a second name corresponding to the second piece of connected equipment, and the second request comprises the second name and an identifier indicating a device discovery link;

The first server responds to the second request and sends second data to the first device, wherein the second data comprises a device discovery communication standard followed by the second internet-enabled device;

The first device runs the second data and sends a second discovery request to the second internet-connected device;

after the first equipment receives second response information, displaying a fourth interface, wherein the second response information is information fed back by the second physical-to-physical equipment, and the second response information carries equipment information of the second physical-to-physical equipment; the fourth interface comprises a second option control, and the second option control is used for displaying equipment information of the second physical connection equipment;

And after the first equipment detects the operation of the user on the second option control, displaying the third interface again, wherein a second management control is added in the third interface, the second management control corresponds to the second internet of things equipment and is used for triggering the sending of a control instruction to the second internet of things equipment, and the second internet of things equipment and the first internet of things equipment come from different manufacturers.

3. The method according to claim 1 or 2, wherein after the first device detects the operation of the first option control by the user, in a scenario where the first device logs in to a first account provided by the first server, the method further comprises:

The first equipment logs in a second account number provided by a second server, wherein the second server is a server corresponding to the first Internet of things equipment;

The first device sends the second account to the first server, instructs the first server and the second server to associate the first account with the second account, and after the first account is associated with the second account, the first account in the first server corresponds to the bound internet of things device under the second account.

4. The method of claim 1, wherein, in the case where a first account and a second account have been associated in the first server, the first device detects a user operation of the first option control, the method further comprising:

The first device sends a fourth request to the first server, wherein the fourth request comprises the first name and an identifier indicating a device binding link;

The first server responds to the fourth request and sends fourth data to the first device, wherein the fourth data comprises a first interface which is required to be called by the first Internet of things device;

And the first device runs the fourth data, and sends a first call request to the first interface of a second server through the first server, wherein the first call request comprises the second account and the device information of the first Internet of things device, and indicates the second server to bind the second account and the first Internet of things device.

5. The method of claim 1 or 2, wherein, in the case where a first account and a second account have been associated in the first server, the first device detects a user operation of the first option control, the method further comprising:

the first device sends a third request to the first server, wherein the third request comprises the first name and an identifier indicating a network distribution link of the device;

the first server responds to the third request and sends fifth data to the first device, wherein the fifth data comprises a device distribution network communication standard followed by the first Internet of things device;

the first device runs the fifth data, and sends token request information to a second server through the first server, wherein the token request information comprises the second account;

After receiving the first token information sent by the second server, the first server sends the first token information to the first device, wherein the first token information corresponds to the second account;

and the first equipment sends a service set identifier, a secret key and first token information of a first network to the first Internet of things equipment, instructs the first Internet of things equipment to join the first network, and requests the second server to bind the equipment information with a second account indicated by the first token information.

6. The method of claim 1 or 2, wherein the first data, the second data, the third data, the fourth data, and the fifth data in the first server are all plug-ins or executable scripts.

7. The method of claim 1 or 2, wherein after the displaying the third interface, the method further comprises: the first device deletes the first data.

8. A device management method applied to a first device, the first device being communicatively coupled to a first server, the method comprising:

responding to a first operation of a user, and displaying a first interface, wherein the first interface is an Internet of things equipment discovery interface;

During the display of the first interface, a first request is sent to the first server in response to received first hot spot information, wherein the first hot spot information is hot spot information broadcasted by first internet of things equipment, the first hot spot information comprises a first name corresponding to the first internet of things equipment, and the first request comprises the first name and an identifier indicating an equipment discovery link;

receiving first data sent by the first server, wherein the first data comprises a device discovery communication standard followed by the first Internet of things device;

operating the first data and sending a first discovery request to the first Internet of things device;

after receiving first response information, displaying a second interface, wherein the first response information is information fed back by the first Internet of things equipment, and the first response information carries equipment information of the first Internet of things equipment; the second interface comprises a first option control, and the first option control is used for displaying equipment information of the first Internet of things equipment;

After detecting the operation of the user on the first option control, sending a third request to the first server, wherein the third request comprises the first name and an identification of an indication equipment network link, and the identification of the indication equipment network link is used for indicating and inquiring equipment network communication standards for the first equipment network link;

Receiving third data fed back by the first server, wherein the third data comprises equipment distribution network communication standards followed by the first Internet of things equipment;

Operating the third data, and sending a service set identifier and a secret key of a first network to the first Internet of things device to instruct the first Internet of things device to join the first network;

9. The method of claim 8, wherein after detecting the user operation of the first option control, in a scenario in which the first device logs in to a first account provided by the first server, the method further comprises:

Logging in a second account provided by a second server, wherein the second server is a server corresponding to the first Internet of things device;

and sending the second account to the first server, and indicating the first server and the second server to associate the first account with the second account, wherein after the first account is associated with the second account, the bound internet of things equipment under the second account corresponds to the first account in the first server.

10. The method of claim 8, wherein, in the case where a first account number and a second account number have been associated in the first server, after detecting the user's operation of the first option control, the method further comprises:

sending a fourth request to the first server, wherein the fourth request comprises the first name and an identifier indicating a binding link of the equipment;

Receiving fourth data fed back by the first server, wherein the fourth data comprises a first interface which is required to be called by the first Internet of things equipment;

And running the fourth data, and sending a first call request to the first interface of a second server through the first server, wherein the first call request comprises the second account and the equipment information of the first Internet of things equipment, and indicates the second server to bind the second account and the first Internet of things equipment.

11. The method of claim 8 or 9, wherein, in the case where a first account and a second account have been associated in the first server, after detecting the user's operation of the first option control, the method further comprises:

sending a third request to the first server, wherein the third request comprises the first name and an identifier of an indication equipment network distribution link;

receiving fifth data fed back by the first server, wherein the fifth data comprises equipment distribution network communication standards followed by the first Internet of things equipment;

Operating the fifth data, and sending token request information to a second server through the first server, wherein the token request information comprises the second account;

Receiving first token information fed back by the second server through the first server, wherein the first token information corresponds to the second account;

And sending a service set identifier, a secret key and first token information of a first network to the first Internet of things device, indicating the first Internet of things device to join the first network, and requesting the second server to bind the device information with a second account indicated by the first token information.

12. The method of any of claims 8-10, wherein after the displaying the third interface, the method further comprises: and deleting the first data.

13. A device management method applied to a first server, the first server being communicatively connected to a first device, the method comprising:

receiving a first request sent by the first device, wherein the first request comprises a first name and an identifier for indicating a device discovery link, the first name is information carried in first hot spot information monitored by the first device, and the first hot spot information is hot spot information broadcasted by first Internet of things equipment;

responding to the first request, and sending first data to the first equipment, wherein the first data comprises equipment discovery communication standards followed by the first Internet of things equipment, and the first equipment is indicated to communicate with the first Internet of things equipment according to the equipment discovery standards carried in the first data;

receiving a third request sent by the first device, wherein the third request comprises the first name and an identifier of an indication device network distribution link, and the identifier of the indication device network distribution link is used for indicating and inquiring a device network distribution communication standard for the network distribution link of the first device;

and responding to the third request, sending third data to the first equipment, wherein the third data comprises equipment distribution network communication standards followed by the first Internet of things equipment, and indicating the first equipment to communicate with the first Internet of things equipment according to the equipment distribution network standards carried in the third data.

14. The method of claim 13, wherein the method further comprises:

Receiving a fourth request sent by the first device, wherein the fourth request comprises the first name and an identifier indicating a device binding link;

And responding to the fourth request, sending fourth data to the first device, wherein the fourth data comprises a first interface which is required to be called by the first Internet of things device, and indicating the first device to bind the first Internet of things device with a corresponding second account by calling the first interface.

15. The method of claim 13 or 14, wherein the first data, the second data, the third data, the fourth data, and the fifth data in the first server are all plug-ins or executable scripts.

16. An electronic device comprising one or more processors and memory; the memory being coupled to a processor, the memory being for storing computer program code comprising computer instructions which, when executed by one or more processors, are for performing the method of any of claims 8-15.

17. A computer storage medium comprising computer instructions which, when run on an electronic device, cause the electronic device to perform the method of any of claims 8-15.