CN117793175A

CN117793175A - Equipment right determining method, device and equipment

Info

Publication number: CN117793175A
Application number: CN202311814318.9A
Authority: CN
Inventors: 周明; 赖立群; 徐晓贤
Original assignee: Hangzhou Hikvision Digital Technology Co Ltd
Current assignee: Hangzhou Hikvision Digital Technology Co Ltd
Priority date: 2023-12-26
Filing date: 2023-12-26
Publication date: 2024-03-29

Abstract

The application provides a device right confirming method, a device and a device, wherein the method comprises the following steps: after the electronic equipment is started, the IP address of the electronic equipment is acquired, and a wired network is accessed based on the IP address of the electronic equipment; if the electronic equipment is not directly connected with the client equipment through the wireless network, a first type prompt is generated; after the first type of physical key operation is obtained, a cloud service registration message is sent to a server, wherein the cloud service registration message comprises a unique equipment identifier of the electronic equipment; if a successful response message returned by the server aiming at the cloud service registration message is received, a second type prompt is generated; when the second type of physical key operation is obtained and the binding message is received, the binding relation between the unique equipment identifier of the electronic equipment and the account number of the user is recorded. Through the technical scheme of the application, the binding security of the electronic equipment can be improved.

Description

Equipment right determining method, device and equipment

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a device authentication method, apparatus, and device.

Background

The electronic device may be composed of hardware and software, and is a device capable of operating independently. The software content of the electronic device only comprises a software running environment and an operating system. The hardware content of the electronic device includes a signal processor, a memory, a communication module, and the like. In some scenarios, the electronic device cannot implement the mass storage function, there is no mass storage medium matching the mass storage function, and the software part has an API (Application Programming Interface, application program interface) programming interface as the core of the development platform.

In order to achieve the certainty of the electronic device, a binding relationship between the user account and the user password needs to be stored by the electronic device. After the electronic device completes the validation, when the electronic device is accessed through the client device, an access message may be sent to the electronic device, and the access message carries the user account and the user password. And when the electronic equipment determines that the user account number and the user password are matched with the stored binding relationship, allowing the client equipment to access.

However, how to implement the right of the electronic device, no reasonable implementation has yet been achieved in the related art.

Disclosure of Invention

The application provides a device authentication method, which is applied to electronic devices and comprises the following steps:

after the electronic equipment is started, acquiring an IP address of the electronic equipment, and accessing a wired network based on the IP address of the electronic equipment;

if the electronic equipment is not directly connected with the client equipment through the wireless network, a first type prompt is generated, and the first type prompt is used for prompting a user to execute a first type physical key operation;

after the first type of physical key operation is obtained, a cloud service registration message is sent to a server, wherein the cloud service registration message comprises a unique equipment identifier of the electronic equipment;

If a success response message returned by the server for the cloud service registration message is received, wherein the success response message indicates that the electronic equipment is successfully registered, a second type prompt is generated, and the second type prompt is used for prompting a user to execute a second type physical key operation;

when the second type of physical key operation is obtained and a binding message is received, the binding message comprises a user account, and the binding relationship between the unique equipment identifier of the electronic equipment and the user account is recorded.

The application provides a device right determining device, which is applied to electronic equipment, and comprises:

the acquisition module is used for acquiring the IP address of the electronic equipment after the electronic equipment is started, and accessing a wired network based on the IP address of the electronic equipment;

the processing module is used for generating a first type prompt if the electronic equipment is not directly connected with the client equipment through the wireless network, wherein the first type prompt is used for prompting a user to execute a first type physical key operation;

the sending module is used for sending a cloud service registration message to the server after the first type of physical key operation is obtained, wherein the cloud service registration message comprises a unique equipment identifier of the electronic equipment;

The processing module is configured to generate a second type of prompt if a success response message returned by the server for the cloud service registration message is received, where the success response message indicates that the electronic device is registered successfully, and the second type of prompt is used to prompt a user to execute a second type of physical key operation;

The application provides an electronic device, comprising: a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor; the processor is configured to execute the machine executable instructions to implement the device authentication method of the above examples of the present application.

As can be seen from the above technical solutions, in the embodiments of the present application, a binding relationship between a user account and a unique device identifier of an electronic device may be recorded in the electronic device, so that a client device may access the electronic device and operate the electronic device. Therefore, even if the electronic equipment cannot be externally connected with the display equipment, the equipment authentication can not be completed through operation equipment such as a mouse, a keyboard and the like, and the equipment authentication of the electronic equipment can also be completed, so that the electronic equipment is a screen-free authentication scheme of the electronic equipment, and the authentication is started and added by utilizing the physical contact of a USB port or a network port of the electronic equipment in the authentication process, so that the binding security of the electronic equipment can be improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following description will briefly describe the drawings that are required to be used in the embodiments of the present application or the description in the prior art, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings may also be obtained according to these drawings of the embodiments of the present application for a person having ordinary skill in the art.

FIG. 1 is a flow diagram of a device authentication method in one embodiment of the present application;

FIG. 2 is a flow diagram of a device authentication method in one embodiment of the present application;

FIG. 3 is a flow diagram of a device authentication method in one embodiment of the present application;

FIG. 4 is a schematic structural view of a device authentication apparatus in one embodiment of the present application;

fig. 5 is a hardware configuration diagram of an electronic device in an embodiment of the present application.

Detailed Description

The terminology used in the embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to any or all possible combinations including one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in embodiments of the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, a first message may also be referred to as a second message, and similarly, a second message may also be referred to as a first message, without departing from the scope of the present application. Depending on the context, furthermore, the word "if" used may be interpreted as "at … …" or "at … …" or "in response to a determination".

In a possible implementation manner, in order to realize device authentication, a display device may be externally connected to the electronic device, and an operation device such as a mouse and a keyboard may be connected to the electronic device, so that the electronic device is operated through the operation device such as the mouse and the keyboard, authentication information such as a user account and a user password is input on the electronic device, and a binding relationship between the user account and the user password is stored by the electronic device, so as to complete device authentication.

However, if the electronic device cannot be externally connected with the display device, the electronic device cannot be operated through the operation device such as a mouse and a keyboard (the operation device needs to be used with the display device, if the electronic device does not have the display device, the electronic device cannot be operated by using the operation device), that is, the device authentication cannot be completed.

In another possible implementation, to implement device authentication, the electronic device may support a local area network function (e.g., the electronic device may support WIFI (Wireless Fidelity, wireless fidelity) function), and the client device may establish a wireless connection with the electronic device through the local area network function and log into a configuration interface of the electronic device. Authentication information such as a user account number and a user password can be input on a configuration interface of the electronic equipment, and the binding relationship between the user account number and the user password is stored by the electronic equipment, so that equipment right confirmation is completed.

However, if the electronic device does not support the lan function (such as WIFI function), the client device cannot log in to the configuration interface of the electronic device through the lan function, and thus cannot complete device authentication.

Aiming at the discovery, the embodiment of the application provides a device right confirming method for realizing device right confirmation on electronic devices. The electronic device in this embodiment may be an embedded device, or may be another type of device, which is not limited in type, and the embedded device is described as an example. The embedded device may be composed of hardware and software, and is a device capable of operating independently, the software content only includes a software running environment and an operating system, and the hardware content includes a signal processor, a memory, a communication module, and the like. The embedded device cannot realize the mass storage function, has no mass storage medium matched with the mass storage function, and the software part takes an API programming interface as the core of the development platform.

The embedded device in this embodiment may be a specified type of embedded device, that is, the device authentication method is used to implement device authentication for the specified type of embedded device. Wherein, the embedded device of the specified type refers to: the embedded device is not connected with the display device (i.e., the embedded device cannot be authorized by the operation device such as a mouse and a keyboard), and the embedded device and the client device do not communicate through the local area network, for example, the embedded device does not support a local area network function (such as a WIFI function), and the embedded device and the client device cannot establish a wireless connection (the client device cannot authenticate the embedded device through a configuration interface of the embedded device).

The device right determination in this embodiment means: and confirming that the user has operation authority on the embedded equipment, and is the owner of the embedded equipment. For example, after the embedded device completes the validation, the embedded device may record a binding relationship between the user account and the unique device identifier of the embedded device, and when the embedded device is accessed through the client device, an access message may be sent to the embedded device, where the access message carries the user account. When the embedded device determines that the user account matches the stored binding relationship (i.e., the binding relationship exists for the user account), the client device is allowed to access the embedded device, i.e., the operation of the embedded device is allowed.

The device authentication method according to the embodiment of the present application is described below with reference to specific embodiments.

Referring to fig. 1, a flow chart of a device authentication method is shown, and the method includes:

step 101, after the embedded device is started, the IP address of the embedded device is obtained, and the wired network is accessed based on the IP address of the embedded device.

The embedded device may be an NVR (Network Video Recorder ) or may be another type of embedded device, which is not limited in type.

For example, the embedded device may be connected to the network device (such as a router or a switch) through a network cable, and after the embedded device is started (such as a start-up or a restart), if the embedded device supports a DHCP (Dynamic Host Configuration Protocol ) function, an IP address of the embedded device may be obtained from a DHCP server (the network device may be used as a DHCP server), that is, an IP address is obtained from the DHCP server, and this IP address is used as an IP address of the embedded device. On this basis, the embedded device can access the wired network based on the IP address of the embedded device.

Illustratively, the DHCP protocol allows a server (e.g., a DHCP server) to dynamically assign an IP address to a client (e.g., an embedded device), so that after the embedded device is booted, the embedded device may obtain the IP address from the DHCP server without limiting the process of obtaining the IP address.

Step 102, after the embedded device is started, if the embedded device is not directly connected with the client device through the wireless network, the embedded device generates a first type of prompt, and the first type of prompt is used for prompting the user to execute a first type of physical key operation, and the first type of prompt can be a prompt tone or a prompt lamp.

Illustratively, to ensure information security of the embedded device, the embedded device initially defaults to not turn on the cloud service. Based on this, the embedded device does not turn on cloud services by default at startup, but generates a first type of hint. For an embedded device supporting the voice prompt function, the first type of prompt may be a prompt tone, e.g., the embedded device may give some prompt tone. For the embedded device supporting the light prompt function, the first type of prompt can also be a prompt lamp, for example, the embedded device can give a certain prompt lamp, for example, the lamp light flashes 3 times, and the like.

For example, after the embedded device is started, if it is known that the embedded device is not directly connected to the client device through the wireless network, and it is known that the embedded device is not connected to the display device, the embedded device may generate a first type of prompt. Otherwise, if it is known that the embedded device is directly connected with the client device through the wireless network, or the embedded device is connected with the display device, then the device authentication can be completed in other manners, and the device authentication process is not limited. For convenience of description, in this embodiment, an example is taken in which the embedded device is not directly connected to the client device through the wireless network, and the embedded device is not connected to the display device.

Step 103, the embedded device detects whether the first type of physical key operation is acquired.

For example, at startup, in addition to generating the first type of prompt, the embedded device may also start a detection thread, through which the first type of physical key operation is detected, i.e., whether the first type of physical key operation is obtained (i.e., by executing the first type of physical key operation on the embedded device).

If the embedded device acquires the first type of physical key operation, step 103 is executed. If the embedded device does not acquire the first type of physical key operation, continuing to detect the first type of physical key operation through the detection thread, and the like until the first type of physical key operation is detected to be acquired.

By way of example, the first type of physical key operation may include, but is not limited to, a network cable plug operation, or a long mouse button press, or a number of mouse button clicks, without limitation to this first type of physical key operation.

For example, after the embedded device generates the first type of prompt, the user may perceive the first type of prompt and learn that the physical key needs to be operated based on the first type of prompt. If the physical key is a plug-in network cable, the user can pull out the network cable of the embedded device and then insert the network cable of the embedded device, namely, plug-in operation is executed aiming at the network cable of the embedded device, and after the embedded device senses the operation, the first type of physical key operation is detected and obtained. For another example, if the physical key is a long mouse key press (e.g., long mouse left and/or right key presses for 5 seconds), the user may press the left or right mouse key for 5 seconds, i.e., long mouse key press operation for the embedded device, and after the embedded device senses the above operation, the embedded device detects and obtains the first type of physical key operation. For another example, if the physical key is the number of mouse clicks (for example, 3 mouse clicks), the user may click the mouse 3 times, and after sensing the above operation, the embedded device detects and obtains the first type of physical key operation. Of course, the foregoing is merely a few examples and is not limiting in this regard.

Step 104, after the embedded device acquires the first type of physical key operation, sending a cloud service registration message to the server, wherein the cloud service registration message comprises a unique device identifier of the embedded device.

The embedded device does not start cloud service by default when being started, and starts cloud service after the first type of physical key operation is acquired, namely, a cloud service process is started, the cloud service process completes device authorization operation, namely, the follow-up process is executed by the cloud service process. Of course, the embodiment is not limited to the cloud service process executing the device authentication operation, as long as the embedded device has the device authentication function.

After the first type of physical key operation is acquired, since the embedded device has accessed the wired network based on the IP address of the embedded device (see step 101), the embedded device may send a cloud service registration message to the server, which may include a unique device identification of the embedded device.

The unique device identifier of the embedded device may be a device serial number of the embedded device, or may be other types of identifiers, which are not limited as long as the unique device identifier can uniquely represent the embedded device. In one possible implementation manner, an identification code (such as a format code, a bar code, a two-dimensional code, etc.) may be attached to a designated location of the embedded device, where the identification code may correspond to a unique identifier of the embedded device, that is, the unique device identifier corresponding to the identification code is stored in the embedded device, and the unique device identifier corresponding to the identification code may be used as the unique device identifier of the embedded device. It should be noted that, when the identification code on the embedded device is scanned by the client device, a unique device identifier corresponding to the identification code may be obtained, that is, a unique corresponding identifier of the embedded device may be obtained.

The sending, by the embedded device, the cloud service registration message to the server may include: and acquiring the stored unique equipment identifier corresponding to the identification code from the embedded equipment, and taking the unique equipment identifier corresponding to the identification code as the unique equipment identifier of the embedded equipment. And then, generating a cloud service registration message, wherein the cloud service registration message comprises a unique equipment identifier corresponding to the identification code, and sending the cloud service registration message to a server. The source IP address of the cloud service registration message may be an IP address obtained by the embedded device through DHCP.

The server may also be called a cloud server, where the cloud server is a server for registration of the embedded device, the cloud server may remotely let the embedded device register, and the cloud server is accessed by the client device.

Step 105, after receiving the cloud service registration message, the server records the corresponding relationship between the unique device identifier of the embedded device and the IP address of the embedded device in the registered list.

For example, the server may maintain a registered list in advance for recording information of all embedded devices that have been successfully registered. Based on this, after receiving the cloud service registration message sent by the embedded device, the server may parse the IP address of the unique device representation of the embedded device and the IP address of the embedded device (i.e., the source IP address of the cloud service registration message) from the cloud service registration message, and record the correspondence between the unique device identifier of the embedded device and the IP address of the embedded device in the registered list.

The embedded device is indicated as being successfully registered by recording the unique device identification of the embedded device in the registered list, that is, by recording the unique device identification of the embedded device in the registered list. In summary, if the unique device identifier of the embedded device is in the registered list, the embedded device is successfully registered, otherwise, if the unique device identifier of the embedded device is not in the registered list, the embedded device is not successfully registered.

Step 106, the server sends a success response message to the embedded device, wherein the success response message is used for indicating that the embedded device is registered successfully. For example, after recording the unique device identifier of the embedded device in the registered list, the server determines that the embedded device is registered successfully, and sends a success response message to the embedded device, where the success response message indicates that the embedded device is registered successfully.

Step 107, the server sends a registration success message to the client device, and the client device receives the registration success message, where the registration success message is used to indicate that the embedded device is registered successfully.

After the first type prompt is generated by the embedded device, the user may scan the identification code on the embedded device through the client device to obtain the unique device identifier corresponding to the identification code, that is, the unique device identifier of the embedded device. For example, an identification code may be attached to a designated location of the embedded device, where the identification code may correspond to a unique device identifier of the embedded device, so that when the identification code on the embedded device is scanned by the client device, the unique device identifier corresponding to the identification code may be obtained.

After knowing the unique device identifier corresponding to the identification code, the client device may send an inquiry message to the server, where the inquiry message may include the unique device identifier corresponding to the identification code, and the inquiry message is used to inquire whether the embedded device corresponding to the unique device identifier is successfully registered. After the client device sends the query message to the server, if the registration success message returned for the query message is received within a preset time period (which may be configured empirically, such as 1 second, etc.), the client device stops sending the query message to the server, that is, the client device successfully receives the registration success message sent by the server.

If the registration success message returned for the query message is not received within the preset duration, the client device continues to send the query message to the server after the preset duration is set, and so on until the client device receives the registration success message sent by the server, the query message is stopped being sent.

Illustratively, each time the server receives an inquiry message sent by the client device, it parses a unique device identifier corresponding to the identification code from the inquiry message, and determines whether the unique device identifier exists in the registered list. If the unique equipment identifier exists in the registered list, the server indicates that the embedded equipment corresponding to the unique equipment identifier is successfully registered, and therefore the server sends a registration success message to the client equipment, wherein the registration success message is used for indicating that the embedded equipment is successfully registered and prompting the client equipment to stop sending the query message. If the unique equipment identifier does not exist in the registered list, the server indicates that the embedded equipment corresponding to the unique equipment identifier is not successfully registered, so that the server does not send a registration success message to the client equipment, the client equipment continues to send an inquiry message until the server continuously judges whether the unique equipment identifier exists in the registered list when receiving the inquiry message next time, and the like until the server sends a registration success message to the client equipment, so that the client equipment can acquire that the embedded equipment is successfully registered.

Step 108, after receiving the registration success message, the client device sends a binding message to the server, where the binding message may include a user account, and the binding message indicates that the user account needs to be bound, that is, triggers the embedded device to bind the relationship between the unique device identifier of the embedded device and the user account.

For example, the client device may obtain a user account, which is a user account used to authenticate the embedded device. For example, when the embedded device needs to be operated through the user account a, the user account that is authorized for the embedded device is the user account a. It should be noted that the user account may be understood as a login account of the client device (i.e. the user account is registered in the client device), i.e. the user may log in to the client device through the user account and then access the embedded device through the client device.

In addition, the user may log in to the client device through a plurality of user accounts (i.e., the user may register a plurality of user accounts), for example, the user may log in to the client device through a user account a and a user account B, in which case, if the user logs in to the client device through the user account a, the embedded device may be accessed through the client device, i.e., the user account a is allowed to operate the embedded device. If the user logs in the client device through the user account B, the user account B is not allowed to operate the embedded device, i.e. the user account B is not an authorized user account of the embedded device, and the embedded device cannot be accessed.

Then, after obtaining the user account, the client device may send a binding message (which may also be referred to as a binding command) to the server, which may include the user account.

Step 109, the server sends the binding message to the embedded device.

In one possible implementation, when the client device sends a binding message to the server, the binding message further includes a unique device identification of the embedded device. For example, when the server sends a registration success message to the client device, the registration success message carries the unique device identifier of the embedded device, and the client device may parse the unique device identifier of the embedded device from the registration success message, and carry the unique device identifier of the embedded device in the binding message. For another example, the client device obtains the unique device identifier corresponding to the identifier by scanning the identifier on the embedded device, and the binding message carries the unique device identifier corresponding to the identifier. Of course, the above are just two examples of sources of unique device identification, and are not limiting.

Illustratively, the server, upon receiving the binding message, parses a unique device identification of the embedded device from the binding message and determines if the unique device identification is present in the registered list. If not, discarding the binding message. If yes, because the registered list is used for recording the corresponding relation between the unique equipment identifier and the IP address, the server inquires the IP address (namely the IP address of the embedded equipment) corresponding to the unique equipment identifier from the registered list, and sends the binding message to the embedded equipment based on the IP address.

Step 110, the embedded device receives the binding message sent by the server.

Step 111, if the embedded device receives a success response message returned by the server for the cloud service registration message, where the success response message indicates that the embedded device is registered successfully, the embedded device generates a second type of prompt, where the second type of prompt is used to prompt the user to execute a second type of physical key operation, and the second type of prompt is a prompt tone or a prompt light.

Illustratively, referring to step 106, after receiving the cloud service registration message, the server may send a success response message to the embedded device, based on which, in step 111, the embedded device may generate a second type of prompt upon receiving this success response message. For an embedded device supporting the voice prompt function, the second type of prompt may be a prompt tone, e.g., the embedded device may give some prompt tone. For the embedded device supporting the light prompt function, the second type of prompt can also be a prompt lamp, for example, the embedded device can give a certain prompt lamp, for example, the lamp light flashes 5 times, etc.

Step 112, the embedded device detects whether the second type of physical key operation is acquired.

For example, when the embedded device receives the success response message, in addition to generating the second type prompt, the embedded device may also start a detection thread, through which the second type physical key operation is detected, that is, whether the second type physical key operation is acquired (that is, by executing the second type physical key operation on the embedded device) is detected. If the embedded device acquires the second type of physical key operation, step 113 is executed. If the embedded device does not acquire the second type of physical key operation, continuing to detect the second type of physical key operation through the detection thread, and the like until the second type of physical key operation is detected to be acquired.

The second type of physical key operation may be the same as or different from the first type of physical key operation. The second type of physical key operation may include, but is not limited to, a network cable plug operation, a long-press operation of a mouse key, or a number of mouse key clicks, which is not limited to this second type of physical key operation.

For example, after the embedded device generates the second type of prompt, the user may perceive the second type of prompt and learn that the physical key needs to be operated based on the second type of prompt. If the physical key is a pluggable network cable, the user can unplug the network cable of the embedded device, then plug the network cable of the embedded device, namely, execute plug operation on the network cable of the embedded device, and after the embedded device senses the operation, detect and acquire the second type of physical key operation. For another example, if the physical key is a long mouse key press (e.g., long mouse left and/or right key presses for 5 seconds), the user may press the left or right mouse key for 5 seconds, i.e., long mouse key press operation for the embedded device, and after the embedded device senses the above operation, the embedded device detects and obtains a second type of physical key operation. For another example, if the physical key is the number of mouse clicks (for example, 3 mouse clicks), the user may click the mouse 3 times, and after sensing the above operation, the embedded device detects and obtains the second type of physical key operation. Of course, the foregoing is merely a few examples and is not limiting in this regard.

Step 113, when the embedded device receives the binding message (including the user account) and obtains the second type of physical key operation, the binding relationship between the unique device identifier of the embedded device and the user account is recorded.

The embedded device obtains the binding of the user trigger device after obtaining the second type of physical key operation, so that the embedded device can analyze the user account number from the binding message and record the binding relationship between the unique device identifier of the embedded device and the user account number. After the binding record is completed, the embedded device may also give a prompt tone or light to indicate that the binding is completed.

Step 114, the embedded device sends the binding relationship to the server, and the server records the binding relationship between the unique device identifier of the embedded device and the user account.

Step 115, the server sends an activation indication message to the client device.

For example, after the embedded device records the binding relationship between the unique device identifier of the embedded device and the user account, the binding relationship is not activated (i.e., not validated), and similarly, after the server records the binding relationship, the binding relationship is not activated (i.e., not validated). On this basis, the server may send an activation indication message to the client device, which is used to trigger the client device to activate (validate) the binding relationship.

Step 116, the client device, after receiving the activation indication message, sends an activation request message to the server, where the activation request message is used to activate (validate) the binding relationship of the embedded device.

For example, if the binding relationship only needs to record the unique device identifier of the embedded device and the user account, the activation request message need not carry the user password (i.e., the user password associated with the user account). If the binding relationship needs to record the unique device identifier, the user account and the user password of the embedded device, the activation request message may further include the user password associated with the user account.

For example, after receiving the activation indication message, the client device may present a configuration interface to the user, and the user inputs the user account and the user password in the configuration interface, so that the client device may obtain the user account and the user password, and send an activation request message to the server, where the activation request message may include the user account and the user password.

Step 117, the server sends the activation request message to the embedded device after receiving the activation request message.

For example, the server may parse the user account and the user password (optionally) from the activation request message, and may query, based on the user account, a binding relationship corresponding to the embedded device, that is, the binding relationship includes a unique device identifier of the user account and the embedded device, and may then activate (take effect) the binding relationship. On the basis, if the activation request message carries the user password, the user password can be added in the binding relationship, namely the binding relationship comprises the user account number, the user password and the unique equipment identifier of the embedded equipment.

The server may query the binding relationship for a unique device identifier of the embedded device, such that the server may query the registered list for an IP address corresponding to the unique device identifier (i.e., the IP address of the embedded device), and send the activation request message to the embedded device based on the IP address.

Step 118, after receiving the activation request message, the embedded device activates (validates) the binding relationship corresponding to the activation request message.

For example, the embedded device may parse the user account and the user password (optional) from the activation request message, and may query a binding relationship based on the user account, that is, the binding relationship includes a unique device identifier of the user account and the embedded device, and may then activate (validate) the binding relationship. On the basis, if the activation request message carries the user password, the user password can be added in the binding relationship, namely the binding relationship comprises the user account number, the user password and the unique equipment identifier of the embedded equipment.

So far, the device authentication of the embedded device is successfully completed, and binding relations are stored in the embedded device and the server. When the client device accesses the embedded device through the server, an access message may be sent to the server, and the access message carries the user account (or user account and password). The server allows the access message to be sent to the embedded device when it determines that the user account matches the stored binding relationship. And when the server determines that the user account is not matched with the stored binding relationship, the access message is not sent to the embedded device. And when the embedded equipment receives the access message, if the user account is determined to be matched with the stored binding relationship, allowing the client equipment to access the embedded equipment, namely allowing the operation of the embedded equipment. And if the user account is not matched with the stored binding relationship, prohibiting the operation of the embedded equipment.

In the device authentication process, the same user account is allowed to be associated with a plurality of embedded devices, namely, the user account is recorded in the binding relation of the plurality of embedded devices, so that the user account can access the plurality of embedded devices, and the plurality of embedded devices provide services for the user account.

In the process of equipment authorization, a plurality of user accounts are allowed to be associated with the same embedded equipment, namely, a plurality of user accounts are recorded in the binding relation of one embedded equipment, so that the plurality of user accounts can access the one embedded equipment, and the one embedded equipment provides services for the plurality of user accounts.

The embedded device may provide video analysis services, but may also provide other services related to video, without limitation. For example, the embedded device may store a large number of video files, the user account accesses the embedded device through the client device, and may retrieve data from the large number of video files of the embedded device, and the embedded device may provide a data retrieval result, and provide an analysis of the data retrieval result, which does not limit the functions of the embedded device.

In one possible implementation manner, the embedded device sends a cloud service disconnection message to the server within a preset first time period (for example, X minutes, X may be configured empirically) after sending the cloud service registration message to the server, and if the binding message is not received, the cloud service disconnection message includes a unique device identifier of the embedded device. After receiving the cloud service disconnection message, the server deletes the corresponding relation between the unique device identifier of the embedded device and the IP address of the embedded device from the registered list, which indicates that the embedded device is an unsuccessfully registered embedded device, and in the subsequent process, the embedded device needs to be re-registered.

For example, the embedded device has an operation flow interruption condition in the operation process, namely, has a binding abnormal condition, in order to prevent risks caused by abnormal operation, if the cloud service is not bound within X minutes after the cloud service is started, the cloud service needs to be disconnected, so that the security risks are reduced. Based on this, the embedded device may start timing after sending the cloud service registration message. If the time length reaches the preset first time length (for example, X minutes), the embedded device receives the binding message, stops timing, and successfully completes binding. If the timing duration reaches the preset first duration, the embedded device still does not receive the binding message, and the embedded device needs to disconnect the cloud service and send a cloud service disconnection message to the server.

After receiving the cloud service disconnection message, the server can delete the corresponding relation between the unique device identifier of the embedded device and the IP address of the embedded device from the registered list, that is, the server finishes the registration of the embedded device, and does not execute the binding flow of the embedded device, thereby reducing the security risk.

In one possible implementation manner, the embedded device deletes the binding relationship if the activation request message is not received within a preset second period (for example, Y minutes, Y may be configured according to experience) after the binding relationship (the binding relationship includes a unique device identifier of the embedded device and a user account number, and does not include a user password corresponding to the user account number) is recorded, and the embedded device sends a cloud service disconnection message to the server, where the cloud service disconnection message includes the unique device identifier of the embedded device. After receiving the cloud service disconnection message, the server deletes the binding relationship corresponding to the embedded device, and deletes the corresponding relationship between the unique device identifier of the embedded device and the IP address of the embedded device from the registered list.

For example, the embedded device has an operation flow interruption condition in the operation process, namely, has a binding abnormal condition, and in order to prevent risks caused by abnormal operation, the cloud service is automatically unbinding and disconnected when the binding account (i.e. the user account) is not activated within Y minutes, so that the security risks are reduced.

Based on this, the embedded device may begin timing after recording the binding between the unique device identification of the embedded device and the user account (step 113). If the timing duration reaches the preset second duration (for example, Y minutes), the embedded device receives the activation request message (namely, completes the activation of the binding relationship), the timing is stopped, and the binding is successfully completed. If the timing duration reaches the preset second duration, the embedded device still does not receive the activation request message, and the embedded device needs to delete the binding relationship and disconnect the cloud service.

When the embedded device disconnects the cloud service, a cloud service disconnection message may be sent to the server. After receiving the cloud service disconnection message, the server deletes the binding relation corresponding to the embedded device, and deletes the corresponding relation between the unique device identifier of the embedded device and the IP address of the embedded device from the registered list, namely, the server finishes the activation of the embedded device, does not execute the binding flow of the embedded device, and reduces the security risk.

In one possible implementation manner, if the binding is not successful within Z minutes after the client initiates the binding, the user is prompted whether the physical key confirmation is added, and if the physical key confirmation is added, the user is recommended to add the binding device by using the display device or the WIFI mode, and the process is not limited. In addition, in order to promote the usability, remind the user through warning light or the mode of warning tone after the defaulting resumes.

For example, the above execution sequence is only an example given for convenience of description, and in practical application, the execution sequence between steps may be changed, which is not limited. Moreover, in other embodiments, the steps of the corresponding methods need not be performed in the order shown and described herein, and the methods may include more or less steps than described herein. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; various steps described in this specification, in other embodiments, may be combined into a single step.

As can be seen from the above technical solutions, in the embodiments of the present application, the client device may complete device authentication through the server, that is, record, at the embedded device, a binding relationship between the user account and a unique device identifier of the embedded device, so that the client device may access the embedded device and operate the embedded device. Therefore, even if the embedded device cannot be externally connected with the display device, the device authentication cannot be completed through operation devices such as a mouse and a keyboard, and the device authentication can be completed through a server, so that the method is a screen-free authentication scheme of the embedded device, and in the authentication process, the authentication is started and added by utilizing the physical contact of a USB port or a network port of the embedded device, so that the binding safety of the embedded device is improved. Under the scene that the embedded device does not have a computer, a WIFI local area network and a display device, the physical contact of a USB port or a network port of the embedded device can be utilized to confirm the starting and adding of the rights. The real-time status of the embedded device may be presented by the status of the sound output and indicator lights. In order to reduce the safety problem caused by misoperation, the cloud service is disconnected again after being registered to the cloud service for X minutes without binding, and if the cloud service is not activated after being bound for Y minutes, the cloud service is automatically unbindled and closed. In order to further increase interactive friendliness, the user is prompted to bind the embedded device in a display device or WIFI mode when the client initiates the binding procedure and is not registered successfully or is bound successfully within Z minutes.

Referring to fig. 2, a flow chart of a device authentication method is shown, and the method includes:

step 201, after the embedded device is started, an IP address of the embedded device is obtained, and a wired network is accessed based on the IP address of the embedded device.

Step 202, after the embedded device is started, if the embedded device is not directly connected to the client device through the wireless network, the embedded device generates a first type of prompt, and the first type of prompt is used for prompting the user to execute a first type of physical key operation, and the first type of prompt can be a prompt tone or a prompt lamp.

Step 203, the embedded device detects whether a first type of physical key operation is acquired. If yes, go to step 204. If not, continuing to detect whether the first type of physical key operation is acquired.

Step 204, after the embedded device obtains the first type of physical key operation, the embedded device sends a cloud service registration message to the server, where the cloud service registration message includes a unique device identifier of the embedded device.

Step 205, after receiving the cloud service registration message, the server records a correspondence between a unique device identifier of the embedded device and an IP address of the embedded device in a registered list.

Step 206, the server sends a success response message to the embedded device, where the success response message is used to indicate that the embedded device has been successfully registered.

Step 207, the server sends a registration success message to the client device, and the client device receives the registration success message, where the registration success message is used to indicate that the embedded device is registered successfully.

For example, steps 201-207 may refer to steps 101-107, which are not described herein.

Step 208, after receiving the registration success message, the client device sends a binding message to the server, where the binding message includes a unique device identifier of the embedded device, a user account, and a user password (the user password is a password associated with the user account, and the user password is optional).

For example, after receiving the registration success message, the client device may present a configuration interface to the user, where the user inputs a user account (a user account for authenticating the embedded device) and a user password associated with the user account, so that the client device may obtain the user account and the user password. The client device may then send a binding message (which may also be referred to as a binding command) to the server, which may include the unique device identification of the embedded device, the user account number, and the user password.

Step 209, the server sends the binding message to the embedded device.

Step 210, the embedded device receives the binding message sent by the server.

Step 211, if the embedded device receives a success response message returned by the server for the cloud service registration message, where the success response message indicates that the embedded device is registered successfully, the embedded device generates a second type prompt, and the second type prompt is used to prompt the user to execute a second type physical key operation.

Step 212, the embedded device detects whether the second type of physical key operation is acquired. If yes, go to step 213. If not, continuing to detect whether the second type of physical key operation is acquired.

For example, steps 209-212 may be referred to as steps 109-112, which are not described herein.

Step 213, when the embedded device receives the binding message and obtains the second type of physical key operation, the binding relationship between the unique device identifier of the embedded device, the user account and the user password is recorded. The user password is optional, that is, the binding relationship may or may not include the user password. After the binding is obtained, the binding may also be validated (activated).

Step 214, the embedded device sends the binding relationship to the server, and the server records the binding relationship, where the binding relationship includes a unique device identifier of the embedded device, a relationship between the user account and the user password. After the binding is obtained, the binding may also be validated (activated).

And the device authentication is successfully completed, and the embedded device and the server are both stored with binding relations.

In one possible implementation manner, the embedded device sends a cloud service disconnection message to the server within a preset first time period (for example, X minutes, X may be configured empirically) after sending the cloud service registration message to the server, and if the binding message is not received, the cloud service disconnection message includes a unique device identifier of the embedded device. After receiving the cloud service disconnection message, the server deletes the corresponding relation between the unique device identification of the embedded device and the IP address of the embedded device from the registered list.

Based on the same application concept as the above method, an apparatus authorization method is provided in the embodiments of the present application, which may be applied to an embedded apparatus, and is shown in fig. 3, and is a flow chart of the method, where the method includes:

Step 301, after the embedded device is started, an IP address of the embedded device is obtained, and a wired network is accessed based on the IP address of the embedded device.

Step 302, if the embedded device is not directly connected to the client device through the wireless network, a first type of prompt is generated, where the first type of prompt is used to prompt the user to execute the first type of physical key operation.

Step 303, after the first type of physical key operation is acquired, a cloud service registration message is sent to the server, where the cloud service registration message may include a unique device identifier of the embedded device.

Step 304, if a success response message returned by the server for the cloud service registration message is received, wherein the success response message indicates that the embedded device is successfully registered, a second type prompt is generated, and the second type prompt is used for prompting the user to execute a second type physical key operation.

Step 305, when the second type of physical key operation is obtained and a binding message is received, where the binding message includes a user account, a binding relationship between a unique device identifier of the embedded device and the user account is recorded.

Illustratively, the embedded device is configured with an identification code, and the embedded device stores a unique device identifier corresponding to the identification code. Based on this, sending a cloud service registration message to the server may include, but is not limited to: acquiring a unique device identifier corresponding to the stored identification code from the embedded device; generating a cloud service registration message including a unique device identification; and sending a cloud service registration message to the server.

Illustratively, after the embedded device sends the cloud service registration message to the server, the unique device identifier of the embedded device is recorded in the registered list by the server based on the cloud service registration message.

Illustratively, the binding message is sent by the client device to the embedded device through the server upon determining that the embedded device has been successfully registered by the client device; after scanning the identification code on the embedded device, the client device sends an inquiry message carrying a unique device identification corresponding to the identification code to the server, wherein the inquiry message is used for inquiring whether the embedded device corresponding to the unique device identification is successfully registered; if the registered list includes the unique device identification, the server sends information that the embedded device has been successfully registered to the client device.

Illustratively, recording the binding of the unique device identification of the embedded device to the user account may include, but is not limited to: if the binding message also comprises a user password corresponding to the user account, recording a unique device identifier of the embedded device and a binding relationship between the user account and the user password. Or if the binding message does not comprise the user password corresponding to the user account, acquiring an activation request message, wherein the activation request message comprises the user password corresponding to the user account, and recording the unique equipment identification of the embedded equipment and the binding relation between the user account and the user password; the method comprises the steps that an activation request message is sent to an embedded device through a server after a client device receives an activation instruction message; the activation indication message is sent to the client device by the server when the server knows that the binding message does not comprise the user password corresponding to the user account.

In an exemplary embodiment, in a preset first time period after the cloud service registration message is sent to the server, if the binding message is not received, a cloud service disconnection message may be sent to the server, where the cloud service disconnection message includes a unique device identifier of the embedded device, and after the cloud service disconnection message is received by the server, the unique device identifier of the embedded device is deleted from the registered list.

If the binding message does not include the user password corresponding to the user account, if the binding message does not receive the activation request message within a preset second time period after the binding relationship is recorded, deleting the binding relationship, sending a cloud service disconnection message to the server, wherein the cloud service disconnection message includes a unique device identifier of the embedded device, and deleting the unique device identifier of the embedded device from the registered list after the server receives the cloud service disconnection message.

Illustratively, the embedded device is not connected to the display device; the second type of physical key operation is the same as or different from the first type of physical key operation; the first type of physical key operation comprises network cable plug operation, or mouse key long-time pressing operation, or mouse key clicking times; the second type of physical key operation comprises a network cable plug operation, or a long-time mouse key pressing operation, or the number of times of clicking the mouse key.

Based on the same application concept as the above method, an apparatus determining device is provided in the embodiment of the present application, and the apparatus determining device may be applied to an electronic apparatus, where the electronic apparatus may be an embedded apparatus according to the above embodiment, as shown in fig. 4, and is a schematic structural diagram of the apparatus, and the apparatus may include:

an obtaining module 41, configured to obtain an IP address of the electronic device after the electronic device is started, and access a wired network based on the IP address of the electronic device;

a processing module 42, configured to generate a first type of prompt if the electronic device and the client device are not directly connected through the wireless network, where the first type of prompt is used to prompt a user to perform a first type of physical key operation;

A sending module 43, configured to send a cloud service registration message to a server after obtaining a first type of physical key operation, where the cloud service registration message includes a unique device identifier of the electronic device;

the processing module 42 is configured to generate a second type of prompt if a success response message returned by the server for the cloud service registration message is received, where the success response message indicates that the electronic device is registered successfully, and the second type of prompt is used to prompt a user to execute a second type of physical key operation;

For example, an identification code is deployed on the electronic device, the electronic device stores a unique device identifier corresponding to the identification code, and the sending module 43 is specifically configured to: acquiring a stored unique equipment identifier corresponding to the identification code from the electronic equipment; generating a cloud service registration message including the unique device identification; and sending a cloud service registration message to the server.

Illustratively, after the sending module 43 sends a cloud service registration message to a server, recording, by the server, a unique device identification of the electronic device in a registered list based on the cloud service registration message; the binding message is sent to the electronic equipment by the client equipment through the server when the client equipment determines that the electronic equipment is successfully registered; after scanning the identification code on the electronic equipment, the client equipment sends an inquiry message carrying a unique equipment identification corresponding to the identification code to a server, wherein the inquiry message is used for inquiring whether the electronic equipment corresponding to the unique equipment identification is successfully registered; and if the registered list comprises the unique equipment identifier, the server sends the information that the electronic equipment is successfully registered to the client equipment.

Illustratively, the processing module 42 is specifically configured to, when recording the binding relationship between the unique device identifier of the electronic device and the user account: if the binding message also comprises a user password corresponding to the user account, recording a unique device identifier of the electronic device and a binding relationship between the user account and the user password; or if the binding message does not include the user password corresponding to the user account, acquiring an activation request message, wherein the activation request message includes the user password corresponding to the user account, and recording a unique device identifier of the electronic device and a binding relationship between the user account and the user password; the activation request message is sent to the electronic equipment through a server after the client equipment receives the activation instruction message; and the activation indication message is sent to the client device when the server knows that the binding message does not comprise the user password corresponding to the user account.

The sending module 43 is further configured to send, within a preset first time period after sending the cloud service registration message to the server, a cloud service disconnection message to the server if the binding message is not received, where the cloud service disconnection message includes a unique device identifier of the electronic device, and after receiving the cloud service disconnection message, the server deletes the unique device identifier of the electronic device from the registered list.

The sending module 43 is further configured to, if the binding message does not include the user password corresponding to the user account, delete the binding relationship and send a cloud service disconnection message to a server if the binding relationship is not received within a preset second duration after recording the binding relationship, where the cloud service disconnection message includes a unique device identifier of the electronic device, and delete the unique device identifier of the electronic device from the registered list after receiving the cloud service disconnection message by the server.

Illustratively, the electronic device is not connected to a display device; the second type physical key operation is the same as or different from the first type physical key operation; the first type of physical key operation comprises network cable plug operation, or mouse key long-time pressing operation, or mouse key clicking times; the second type of physical key operation comprises network cable plugging operation, or mouse key long-pressing operation, or mouse key clicking times.

Based on the same application concept as the above method, an electronic device (such as the embedded device of the above embodiment) is proposed in the embodiment of the present application, and as shown in fig. 5, the electronic device includes: a processor 51 and a machine-readable storage medium 52, the machine-readable storage medium 52 storing machine-executable instructions executable by the processor 51; the processor 51 is configured to execute machine executable instructions to implement the device authentication method disclosed in the above examples of the present application.

Based on the same application concept as the above method, the embodiment of the application further provides a machine-readable storage medium, where a number of computer instructions are stored on the machine-readable storage medium, and when the computer instructions are executed by a processor, the method for device authentication disclosed in the above example of the application can be implemented.

Wherein the machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that can contain or store information, such as executable instructions, data, or the like. For example, a machine-readable storage medium may be: RAM (Radom Access Memory, random access memory), volatile memory, non-volatile memory, flash memory, a storage drive (e.g., hard drive), a solid state drive, any type of storage disk (e.g., optical disk, dvd, etc.), or a similar storage medium, or a combination thereof.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer entity or by an article of manufacture having some functionality. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in one or more software and/or hardware elements when implemented in the present application.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Moreover, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims

1. A device authentication method, applied to an electronic device, the method comprising:

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the electronic device is provided with an identification code, the electronic device stores a unique device identifier corresponding to the identification code, and the sending of the cloud service registration message to the server comprises the following steps:

acquiring a stored unique equipment identifier corresponding to the identification code from the electronic equipment;

generating a cloud service registration message including the unique device identification;

and sending the cloud service registration message to the server.

3. The method of claim 2, wherein the step of determining the position of the substrate comprises,

after the electronic equipment sends a cloud service registration message to a server, the server records the unique equipment identification of the electronic equipment in a registered list based on the cloud service registration message;

the binding message is sent to the electronic equipment by the client equipment through the server when the client equipment determines that the electronic equipment is successfully registered; after scanning the identification code on the electronic equipment, the client equipment sends an inquiry message carrying a unique equipment identification corresponding to the identification code to a server, wherein the inquiry message is used for inquiring whether the electronic equipment corresponding to the unique equipment identification is successfully registered; and if the registered list comprises the unique equipment identifier, the server sends the information that the electronic equipment is successfully registered to the client equipment.

4. The method of claim 1, wherein the recording the binding of the unique device identification of the electronic device to the user account comprises:

if the binding message also comprises a user password corresponding to the user account, recording a unique device identifier of the electronic device and a binding relationship between the user account and the user password; or,

if the binding message does not comprise the user password corresponding to the user account, acquiring an activation request message, wherein the activation request message comprises the user password corresponding to the user account, and recording a unique device identifier of the electronic device and a binding relationship between the user account and the user password;

the activation request message is sent to the electronic equipment through a server after the client equipment receives the activation instruction message; and the activation indication message is sent to the client device when the server knows that the binding message does not comprise the user password corresponding to the user account.

5. The method according to claim 1, wherein the method further comprises:

and in a preset first time period after the cloud service registration message is sent to the server, if the binding message is not received, sending a cloud service disconnection message to the server, wherein the cloud service disconnection message comprises the unique equipment identifier of the electronic equipment, and deleting the unique equipment identifier of the electronic equipment from the registered list after the cloud service disconnection message is received by the server.

6. The method according to claim 4, wherein the method further comprises:

if the binding information does not comprise the user password corresponding to the user account, deleting the binding relation within a preset second time length after the binding relation is recorded, if the activation request information is not received, sending a cloud service disconnection message to the server, wherein the cloud service disconnection message comprises the unique equipment identifier of the electronic equipment, and deleting the unique equipment identifier of the electronic equipment from the registered list after the server receives the cloud service disconnection message.

7. The method according to any one of claims 1 to 6, wherein,

the electronic device is not connected with the display device; the second type physical key operation is the same as or different from the first type physical key operation; the first type of physical key operation comprises network cable plug operation, or mouse key long-time pressing operation, or mouse key clicking times; the second type of physical key operation comprises network cable plugging operation, or mouse key long-pressing operation, or mouse key clicking times.

8. A device authentication apparatus, for application to an electronic device, the apparatus comprising:

9. The apparatus of claim 8, wherein the device comprises a plurality of sensors,

The electronic equipment is provided with an identification code, the electronic equipment stores a unique equipment identifier corresponding to the identification code, and the sending module is specifically used for sending a cloud service registration message to the server: acquiring a stored unique equipment identifier corresponding to the identification code from the electronic equipment; generating a cloud service registration message including the unique device identification; sending a cloud service registration message to the server;

after the sending module sends a cloud service registration message to a server, the server records the unique equipment identification of the electronic equipment in a registered list based on the cloud service registration message; the binding message is sent to the electronic equipment by the client equipment through the server when the client equipment determines that the electronic equipment is successfully registered; after scanning the identification code on the electronic equipment, the client equipment sends an inquiry message carrying a unique equipment identification corresponding to the identification code to a server, wherein the inquiry message is used for inquiring whether the electronic equipment corresponding to the unique equipment identification is successfully registered; if the registered list comprises the unique equipment identifier, the server sends information that the electronic equipment is successfully registered to the client equipment;

The processing module records a binding relationship between a unique device identifier of the electronic device and the user account, and is specifically configured to: if the binding message also comprises a user password corresponding to the user account, recording a unique device identifier of the electronic device and a binding relationship between the user account and the user password; or if the binding message does not include the user password corresponding to the user account, acquiring an activation request message, wherein the activation request message includes the user password corresponding to the user account, and recording a unique device identifier of the electronic device and a binding relationship between the user account and the user password; the activation request message is sent to the electronic equipment through a server after the client equipment receives the activation instruction message; the activation indication message is sent to the client device when the server knows that the binding message does not comprise the user password corresponding to the user account;

the sending module is further configured to send a cloud service disconnection message to a server within a preset first time period after sending a cloud service registration message to the server, if the binding message is not received, where the cloud service disconnection message includes a unique device identifier of the electronic device, and after receiving the cloud service disconnection message, the server deletes the unique device identifier of the electronic device from the registered list;

The sending module is further configured to, if the binding message does not include a user password corresponding to the user account, delete the binding relationship and send a cloud service disconnection message to a server if the binding message does not receive the activation request message within a preset second duration after the binding relationship is recorded, where the cloud service disconnection message includes a unique device identifier of the electronic device, and delete the unique device identifier of the electronic device from the registered list after the server receives the cloud service disconnection message;

wherein the electronic device is not connected to a display device; the second type physical key operation is the same as or different from the first type physical key operation; the first type of physical key operation comprises network cable plug operation, or mouse key long-time pressing operation, or mouse key clicking times; the second type of physical key operation comprises network cable plugging operation, or mouse key long-pressing operation, or mouse key clicking times.

10. An electronic device, comprising: a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor; the processor is configured to execute machine executable instructions to implement the method of any of claims 1-7.