Control method and device of equipment, electronic equipment, storage medium and program product

Abstract

This disclosure relates to a device control method, apparatus, electronic device, storage medium, and program product. The method includes: in response to a first device receiving a target operation instruction, determining a target control instruction, wherein the target control instruction is used to instruct a second device to perform a target operation, the second device being at least one device in a device domain where the first device resides, and the first device being a core device in the device domain; and sending the target control instruction to the second device. In this disclosure, the first device and the second device are located in the same device domain. Control between two devices in the same device domain is secure. Therefore, when the first device controls the second device in its device domain to perform a target operation, no additional authentication is required, thus improving the convenience of cross-device control while ensuring its security.

Description

Technical Field

[0001] This disclosure relates to the field of electronic information technology, and in particular to control methods, devices, electronic equipment, storage media, and program products for equipment. Background Technology

[0002] Cross-device information interaction is an important direction for the future development of smart devices. Current smart devices support identity authentication functions. When extended to cross-device scenarios, related technologies can allow users to authenticate their identities on one device for other devices. After successful authentication, users can directly control other devices across devices, such as unlocking and locking them. However, users still need to authenticate their identities each time they use a cross-device device to determine whether they are the real and legitimate user of the other device, making the control operation relatively cumbersome. Summary of the Invention

[0003] To overcome the problems existing in the related technologies, this disclosure provides a control method, apparatus, electronic device, storage medium, and program product for a device.

[0004] According to a first aspect of the present disclosure, a method for controlling a device is provided, the method comprising:

[0005] In response to the first device receiving a target operation instruction, a target control instruction is determined, wherein the target control instruction is used to instruct a second device to perform the target operation, the second device is at least one device in the device domain where the first device is located, the first device is a core device in the device domain, and the core device has the authority to control other devices in the device domain;

[0006] Send the target control command to the second device.

[0007] Optionally, the target determination control command includes:

[0008] The target control instruction is determined based on the device authentication information of the first device, wherein the device authentication information includes an authentication result and a first device identifier of the first device, the authentication result indicating whether the first device has passed device identity authentication, and the target control instruction is used to instruct the second device to perform the target operation when the authentication result indicates that the first device has passed device identity authentication and the first device identifier indicates that the first device is a core device.

[0009] Optionally, the device authentication information further includes security verification information, and determining the target control command based on the device authentication information of the first device includes:

[0010] Send a target acquisition instruction to the second device, so that the second device generates security verification information upon receiving the target acquisition instruction, wherein the target acquisition instruction is used to acquire the security verification information;

[0011] Receive the security verification information sent by the second device;

[0012] The target control command is generated based on the authentication result, the first device identifier, and the security verification information.

[0013] Optionally, the device authentication information further includes a first device certificate for the first device, and generating the target control command based on the authentication result, the first device identifier, and the security verification information includes:

[0014] The authentication result, the first device identifier, and the security verification information are concatenated to obtain candidate control information;

[0015] The candidate control information is signed using the first device certificate of the first device to obtain the target control command.

[0016] Optionally, sending the target control command to the second device includes:

[0017] Send the target control command to the second device that has identity authentication function;

[0018] The method further includes:

[0019] A preset control command is sent to the second device, which does not have an authentication function, and the preset control command is used to control the second device, which does not have an authentication function, to perform the target operation.

[0020] Optionally, the method further includes:

[0021] Obtain the second device identifier of the third device, wherein the third device includes other devices in the device domain besides the first device;

[0022] The third device is added to the device domain based on the first device identifier and the second device identifier.

[0023] Optionally, adding the third device to the device domain based on the first device identifier and the second device identifier includes:

[0024] The third device is authenticated based on the second device identifier to obtain the authentication result of the third device. The authentication result is determined by the third device based on the second authentication information input by the user.

[0025] Based on the identity authentication result, the first device identifier is sent to the third device so that the third device stores the first device identifier in the first preset identifier set.

[0026] Optionally, sending the first device identifier to the third device based on the authentication result includes:

[0027] If the identity authentication result indicates that the third device has passed device identity authentication, obtain the second device certificate of the third device;

[0028] If the second device certificate is successfully authenticated, the first device identifier is sent to the third device.

[0029] Optionally, adding the third device to the device domain based on the first device identifier and the second device identifier further includes:

[0030] In the case where the third device is a core device, the second device identifier is stored in the second preset identifier set of the first device.

[0031] According to a second aspect of the present disclosure, a method for controlling a device is provided, the method comprising:

[0032] In response to receiving a target control command from a first device, the second device executes the target operation indicated by the target control command, wherein the second device is at least one device in the device domain in which the first device is located, the first device is a core device in the device domain, and the core device has the authority to control other devices in the device domain.

[0033] Optionally, the target control instruction includes device authentication information of the first device, the device authentication information including authentication result and a first device identifier of the first device, the authentication result indicating whether the first device has passed device identity authentication; the execution of the target operation indicated by the target control instruction includes:

[0034] The target operation is performed when the authentication result indicates that the first device has passed device identity authentication and the first device is determined to be a core device in the device domain based on the first device identifier.

[0035] Optionally, the device authentication information further includes security verification information; the method further includes:

[0036] In response to a target acquisition instruction sent by the first device, the security verification information is generated; the target acquisition instruction is sent by the first device upon receiving the target operation instruction, and the target acquisition instruction is used to acquire the security verification information.

[0037] The security verification information is sent to the first device so that the first device generates the device authentication information based on the authentication result, the first device identifier, and the security verification information.

[0038] Optionally, the execution of the target operation indicated by the target control command includes:

[0039] The security verification information is then subjected to security verification.

[0040] If the authentication result indicates that the first device has passed device identity authentication, and the first device is determined to be a core device in the device domain based on the first device identifier, and the security verification of the security verification information has passed, then the target operation indicated by the target control command is executed.

[0041] Optionally, the device authentication information further includes a first device certificate of the first device, which is used to sign the candidate control information obtained by concatenating the authentication result, the first device identifier, and the security verification information; the execution of the target operation indicated by the target control command includes:

[0042] Perform legal authentication on the first device certificate;

[0043] If the authentication result indicates that the first device has passed device identity authentication, and the first device is determined to be a core device in the device domain based on the first device identifier, and the security verification information is verified and the first device certificate is legally authenticated, then the target operation indicated by the target control command is executed.

[0044] Optionally, the method further includes:

[0045] If the preset rejection conditions are met, the target operation will not be executed.

[0046] The target operation indicated by the target control command includes:

[0047] If the preset rejection condition is not met, the target operation is performed;

[0048] The preset rejection condition includes at least one of the following:

[0049] The authentication result indicates that the first device failed device identity authentication;

[0050] Based on the first device identifier, it is determined that the first device and the second device are not in the same device domain;

[0051] The security verification of the security verification information failed.

[0052] The authentication of the first device certificate failed.

[0053] Optionally, the method further includes:

[0054] If the preset rejection condition is met, record the number of failures;

[0055] If the number of failures exceeds a preset number, the target control command will be refused to be responded to within a preset waiting time.

[0056] Optionally, determining that the first device is a core device in the device domain based on the first device identifier includes:

[0057] If the first device identifier is included in the third preset identifier set stored in the second device, the first device is determined to be a core device in the device domain.

[0058] Optionally, the target operation includes an unlocking operation, and the method further includes:

[0059] If the unlocking time exceeds the preset unlocking time, the second device is locked.

[0060] According to a third aspect of the present disclosure, a control device for an apparatus is provided, the device comprising:

[0061] The determination module is configured to determine a target control instruction in response to a first device receiving a target operation instruction, wherein the target control instruction is used to instruct a second device to perform the target operation, the second device is at least one device in the device domain where the first device is located, the first device is a core device in the device domain, and the core device has the authority to control other devices in the device domain;

[0062] The sending module is configured to send the target control command to the second device.

[0063] According to a fourth aspect of the present disclosure, a control device for an apparatus is provided, the device comprising:

[0064] The execution module is configured to execute the target operation indicated by the target control instruction in response to the second device receiving a target control instruction sent by the first device, wherein the second device is at least one device in the device domain in which the first device is located, the first device is a core device in the device domain, and the core device has the authority to control other devices in the device domain.

[0065] According to a fifth aspect of the present disclosure, an electronic device is provided, comprising:

[0066] processor;

[0067] Memory used to store processor-executable instructions;

[0068] The processor is configured to execute the computer program in the memory to implement the steps of the method described in the first aspect of the present disclosure.

[0069] According to a sixth aspect of the present disclosure, an electronic device is provided, comprising:

[0070] processor;

[0071] Memory used to store processor-executable instructions;

[0072] The processor is configured to execute the computer program in the memory to implement the steps of the method described in the second aspect of the present disclosure.

[0073] According to a seventh aspect of the present disclosure, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps of the method described in the first aspect of the present disclosure.

[0074] According to an eighth aspect of the present disclosure, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps of the method described in the second aspect of the present disclosure.

[0075] According to a ninth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the method described in the first aspect of the present disclosure.

[0076] According to a tenth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the method described in the second aspect of the present disclosure.

[0077] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects:

[0078] In this disclosure, after receiving a target operation instruction, the first device determines a target control instruction to instruct the second device to perform the target operation, and sends the target control instruction to the second device in the same device domain as the first device. Since the first and second devices in this disclosure are located in the same device domain, control between two devices in the same domain is secure. Therefore, when the first device controls the second device in its device domain to perform the target operation, no additional authentication is required, thus improving the convenience of cross-device control while ensuring its security.

[0079] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0080] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0081] Figure 1 This is a flowchart illustrating a control method for a device according to an exemplary embodiment.

[0082] Figure 2 This is a schematic diagram illustrating a device classification rule according to an exemplary embodiment.

[0083] Figure 3 This is a schematic diagram illustrating a device classification according to an exemplary embodiment.

[0084] Figure 4 This is a flowchart illustrating another method for controlling a device according to an exemplary embodiment.

[0085] Figure 5 This is a flowchart illustrating another method for controlling a device according to an exemplary embodiment.

[0086] Figure 6 This is a flowchart illustrating another method for controlling a device according to an exemplary embodiment.

[0087] Figure 7 This is a flowchart illustrating another method for controlling a device according to an exemplary embodiment.

[0088] Figure 8 This is a flowchart illustrating another method for controlling a device according to an exemplary embodiment.

[0089] Figure 9 It is based on Figure 8 An embodiment illustrates a flowchart of a device locking process.

[0090] Figure 10 This is a schematic diagram illustrating a device authentication method according to an exemplary embodiment.

[0091] Figure 11 This is a schematic diagram illustrating a device certificate authentication according to an exemplary embodiment.

[0092] Figure 12 This is a schematic diagram illustrating a storage device identifier according to an exemplary embodiment.

[0093] Figure 13 This is a schematic diagram illustrating a process for global unlocking according to an exemplary embodiment.

[0094] Figure 14 This is a schematic diagram illustrating a core device identity authentication process according to an exemplary embodiment.

[0095] Figure 15 This is a schematic diagram illustrating a process for generating and verifying a trusted token according to an exemplary embodiment.

[0096] Figure 16 This is a block diagram illustrating a control device for an apparatus according to an exemplary embodiment.

[0097] Figure 17 This is a block diagram of a control device for another device according to an exemplary embodiment.

[0098] Figure 18 This is a block diagram of a control device for another device according to an exemplary embodiment.

[0099] Figure 19 This is a block diagram of a control device for another device according to an exemplary embodiment.

[0100] Figure 20 This is a block diagram of a control device for another device according to an exemplary embodiment.

[0101] Figure 21 This is a block diagram illustrating an electronic device according to an exemplary embodiment. Detailed Implementation

[0102] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0103] The embodiments described in the following examples of this disclosure are not representative of all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0104] It should be noted that all actions involving the acquisition of signals, information, or data in this disclosure are carried out in compliance with the relevant data protection laws and policies of the country where the location is situated, and with authorization from the owner of the relevant device.

[0105] Before introducing the control method, apparatus, electronic device, storage medium, and program product of the device shown in the embodiments of this disclosure, the application scenarios of the embodiments of this disclosure will be introduced first.

[0106] In cross-device control scenarios, related technologies allow users to authenticate themselves on one device while controlling other devices. Once authenticated, users can directly control these devices across platforms, performing actions such as unlocking, locking, powering on, and powering off. However, for example, unlocking still requires authentication each time a user uses a cross-device device to verify their legitimacy, making the process cumbersome. Currently, there's a solution that unlocks devices without authentication, using a wristband or watch physically linked to the user. This leverages the user-linked nature of wristbands and watches, assuming the user wearing the wristband is the actual user. However, this unlocking method has low security.

[0107] The first device and the second device in this disclosure are located in the same device domain. Control between two devices in the same device domain is secure. Therefore, when the first device controls the second device in the same device domain to perform the target operation, no additional authentication is required. This ensures the security of cross-end control while improving the convenience of cross-end control.

[0108] The embodiments disclosed herein can be applied not only to cross-terminal unlocking and locking functions, but also extended to any cross-terminal control function such as the on / off function of a global remote control.

[0109] Figure 1 This is a flowchart illustrating a control method for a device according to an exemplary embodiment, such as... Figure 1 As shown, the method may include:

[0110] Step S101: In response to the first device receiving the target operation instruction, a target control instruction is determined, wherein the target control instruction is used to instruct the second device to perform the target operation, the second device is at least one device in the device domain where the first device is located, and the first device is a core device in the device domain.

[0111] Step S102: Send the target control command to the second device.

[0112] For example, the first device and the second device can be devices in the same device domain. Here, a device domain can be understood as a set of devices obtained by binding multiple devices that have been pre-authenticated. The bound devices will belong to only one user, so that the devices in the entire device domain trust each other, that is, cross-end control between devices in the same device domain is secure.

[0113] Each device can be arranged according to Figure 2 Classify according to the classification rules shown. Figure 2 Only a selection of smart devices are shown as examples; any smart device with interconnectivity can be added to the device domain. Security levels are categorized by whether they possess a TEE (Trusted Execution Environment) or SE (Secure Element). Having a TEE / SE indicates a higher level of security and can serve as an entry point for user authentication. Performance also plays a role; different smart devices have varying functionalities. For example, smartphones have the most powerful functionality and hold a higher position in the ecosystem, making them suitable as core devices for binding with other devices.

[0114] Devices within a device domain can include core devices and non-core devices. Core devices are those with the authority to control other devices within the device domain; in other words, core devices can control other devices within the device domain across different endpoints. Non-core devices are those that do not have the authority to control other devices within the device domain. For example, see [link to example]. Figure 3 Devices with high security levels, powerful performance, and comprehensive functions, such as mobile phones, tablets, and in-vehicle systems, can be considered core devices in the device domain, while devices with low security levels and insufficient performance, such as PCs (Personal Computers), watches, wristbands, and televisions, can be considered non-core devices in the device domain.

[0115] In this embodiment of the disclosure, the first device may be a core device in a device domain, and the second device may be a core device or a non-core device. The second device may be one or more devices in the device domain. The first device may control the second device to perform a target operation, wherein the target operation may be any operation targeting the second device, such as an unlock operation, a lock operation, a start operation, or a power-off operation.

[0116] In some embodiments, the first device may display a target component on a display interface to prompt the user to perform a target operation on other devices in the device domain. The first device may select a second device to be controlled from the other devices displayed by the target component and trigger a target operation instruction for the target component. The target operation instruction may be triggered, for example, by the user clicking a preset confirmation button. Upon receiving the target operation instruction, the first device can determine that the user needs to control the second device, and can then generate a target control instruction and send it to the second device. After receiving the target control instruction sent by the first device, the second device can perform the target operation according to the instructions of the target control instruction.

[0117] In summary, after receiving the target operation instruction, the first device in this disclosure determines the target control instruction used to instruct the second device to execute the target operation, and sends the target control instruction to the second device in the device domain where the first device is located. Since the first device and the second device in this disclosure are in the same device domain, control between two devices in the same device domain is secure. Therefore, when the first device controls the second device in its device domain to execute the target operation, no additional authentication is required, thus improving the convenience of cross-end control while ensuring its security.

[0118] In other embodiments, one implementation of step S101 may be:

[0119] The target control command is determined based on the device authentication information of the first device, wherein the device authentication information includes the authentication result and the first device identifier of the first device.

[0120] For example, a user can authenticate their identity on the first device to verify whether the user using the second device is a legitimate user. Authentication methods include, but are not limited to, facial recognition, fingerprint recognition, and password authentication. Device authentication information can then be generated based on the authentication result and the first device's identifier. Furthermore, a target control instruction can be generated based on the device authentication information. The authentication result indicates whether the first device has passed device authentication, and the target control instruction instructs the second device to perform a target operation if the authentication result indicates that the first device has passed device authentication and the first device is identified as a core device based on its identifier.

[0121] It should be noted that users only need to authenticate themselves when unlocking the first device and obtain the authentication result. When the first device receives the target operation command, it does not need to repeat the authentication process. Instead, it can generate device authentication information based on the authentication result obtained when unlocking the first device, which improves the convenience of cross-device control while ensuring security.

[0122] After receiving the target control command, the second device can verify the authentication result to determine whether the second device has passed the authentication. It then searches for the first device's identifier in a third preset identifier set stored in the second device. This third preset identifier set can include the device identifiers of all core devices in the device domain where the second device resides. If the third preset identifier set includes the first device's identifier, it indicates that the first and second devices are in the same device domain, and the first device is a core device in that domain. Since the first and second devices have already undergone mutual trust authentication when bound to the same device domain, if the authentication result indicates that the first device has passed the authentication, then it can be determined that the control operation of the first device is secure, and the target operation indicated by the target control command can be executed without requiring additional authentication of the first device to verify the user's identity.

[0123] Figure 4 This is a flowchart illustrating another method for controlling a device according to an exemplary embodiment, such as... Figure 4 As shown, step S101 can be achieved through the following steps:

[0124] Step S1011: In response to the target operation instruction, a target acquisition instruction is sent to the second device so that the second device generates security verification information upon receiving the target acquisition instruction. The target acquisition instruction is used to acquire the security verification information.

[0125] Step S1012: Receive security verification information sent by the second device.

[0126] Step S1013: Generate target control instructions based on the authentication result, the first device identifier, and the security verification information.

[0127] For example, a user can operate on the display interface of the first device to trigger a target operation command, whereby the target operation command can represent controlling the second device to perform the target operation. After receiving the target operation command, the first device can generate a target acquisition command and send it to the second device, whereby the target acquisition command can be used to obtain security verification information. After receiving the target acquisition command, the second device can generate security verification information and send it to the first device.

[0128] In some embodiments, the device authentication information may further include security verification information. After receiving the security verification information, the first device may generate device authentication information based on the authentication result, the first device identifier, and the security verification information.

[0129] While verifying the authentication result and the first device identifier, the second device can also verify the security verification information to prevent replay attacks, thereby further ensuring the security of the device authentication information sent by the first device. If the authentication result indicates that the first device has passed device identity authentication, and the first device identifier determines that the first device and the second device are in the same device domain, and the security verification information has passed security verification, then the second device can determine that the control operation of the first device is secure and can execute the target operation indicated by the target control command.

[0130] In other embodiments, after generating security verification information, the second device can store the security verification information locally. After receiving the security verification information sent by the first device, it can compare the security verification information sent by the first device with the locally stored security verification information. The security verification information may include a timestamp corresponding to the generation time. If the security verification information sent by the first device is the same as the locally stored security verification information, and the timestamp indicates that the security verification information is within a valid duration, then the security verification of the security verification information can be determined to have passed. Conversely, if the security verification information sent by the first device is different from the locally stored security verification information, or the timestamp indicates that the security verification information is not within a valid duration, then the security verification of the security verification information can be determined to have failed.

[0131] In other embodiments, the device authentication information may also include the first device certificate of the first device, and step S101 may also be implemented in the following ways:

[0132] The authentication result, the first device identifier, and the security verification information are combined to obtain candidate control information.

[0133] The candidate control information is signed using the first device certificate of the first device to obtain the target control command.

[0134] For example, to further ensure the security and legitimacy of the first device controlling the second device, the first device can concatenate the authentication result, the first device identifier, and the security verification information to obtain candidate control information. Then, the first device can sign the candidate control information using its first device certificate to obtain device authentication information.

[0135] After receiving the device authentication information, the second device can verify the legitimacy of the first device's certificate. If the first device's certificate passes the legitimacy verification, then the first device can be determined to be a legitimate device. If the authentication result indicates that the first device has passed device identity authentication, and the second device is determined to be in the same device domain as the first device based on the first device's identifier, and the security verification information and the first device's certificate have passed the legitimacy authentication, then the control operation of the first device can be determined to be secure, and the target operation indicated by the target control command can be executed. In this way, by verifying the device identity authentication result, the first device identifier, the security verification information, and the first device certificate, and executing the target operation indicated by the target control command only after all information has passed verification, the security and legitimacy of the first device controlling the second device can be improved.

[0136] In other embodiments, one implementation of step S102 may be:

[0137] Send target control commands to a second device that has authentication capabilities.

[0138] Correspondingly, preset control commands can be sent to a second device that does not have authentication capabilities. These preset control commands are used to control the second device, which does not have authentication capabilities, to perform the target operation.

[0139] For example, a second device with authentication capabilities could be a core device in a device domain, while a second device without authentication capabilities could be a non-core device in the same device domain. For a second device with authentication capabilities, the first device can send a target control command to control the authenticated second device to perform a target operation.

[0140] Since non-core devices lack authentication capabilities, they also lack the locking and unlocking capabilities protected by authentication functions. After such devices are bound to a global smart device, this embodiment can add additional authentication capabilities, enabling devices lacking authentication capabilities to have an additional locking function, allowing the core device to perform authentication on their behalf. Therefore, for a second device lacking authentication capabilities, there is no need to verify device authentication information; the first device can directly send a preset control command to control its unlocking or locking. Users can choose whether to enable the additional locking function; if they choose not to enable it, both direct use and indirect use via the core device will be permitted. This improves the security of devices lacking authentication capabilities, preventing unauthorized users from using such devices.

[0141] Figure 5 This is a flowchart illustrating another method for controlling a device according to an exemplary embodiment, such as... Figure 5 As shown, the method may further include:

[0142] Step S105: Obtain the second device identifier of the third device, wherein the third device may include other devices in the device domain besides the first device.

[0143] Step S106: Add the third device to the device domain based on the first device identifier and the second device identifier.

[0144] For example, during the device domain setup phase, a user can select any core device as the configuration entry point and then choose connectable devices within that core device. It's important to note that a user may have multiple core devices, but only one core device needs to be configured during the initial setup.

[0145] In some embodiments, the first device can be used as the entry point for setting up the device domain. For the selected third device, the user can authenticate on each third device to be added to the device domain. If the authentication is successful, it proves that the user is a real and legitimate user of the third device, and the third device can be added to the device domain to ensure the security of cross-device control of devices in the device domain.

[0146] In other embodiments, a second device identifier of the third device can first be obtained, and the third device can be authenticated based on the second device identifier to obtain an authentication result. This authentication result is determined by the third device based on the second authentication information input by the user. Then, a first device identifier can be sent to the third device based on the authentication result, causing the third device to store the first device identifier in a first preset identifier set. When the first preset identifier set of the third device contains the first device identifier, it can be considered that the third device has been added to a device domain.

[0147] In other embodiments, if the identity authentication result indicates that the third device has passed the device identity authentication, the first device can further obtain the second device certificate of the third device and authenticate the legality of the second device certificate. If the legality authentication of the second device certificate is successful, it means that the second device certificate is legal, and then the first device identifier can be sent to the third device.

[0148] In other embodiments, if the third device is a core device, the first device may also store the second device identifier of the third device in the first device's second preset identifier set to ensure that the first device stores the device identifiers of all core devices. When the device identifiers of all core devices are stored in both the first device and each third device, the device domain establishment process can be considered complete. Thus, after the device domain is established, when the core device controls other devices in the device domain to perform target operations, the other devices only need to verify whether the core device's device identifier is stored in the preset identifier set to determine the security of the core device, without requiring additional authentication to verify the user's identity.

[0149] In summary, after receiving the target operation instruction, the first device in this disclosure determines the target control instruction used to instruct the second device to execute the target operation, and sends the target control instruction to the second device in the device domain where the first device is located. Since the first device and the second device in this disclosure are in the same device domain, control between two devices in the same device domain is secure. Therefore, when the first device controls the second device in its device domain to execute the target operation, no additional authentication is required, thus improving the convenience of cross-end control while ensuring its security.

[0150] Figure 6 This is a flowchart illustrating another method for controlling a device according to an exemplary embodiment, such as... Figure 6 As shown, the method includes:

[0151] Step S201: In response to the second device receiving the target control command sent by the first device, the target operation indicated by the target control command is executed. The second device is at least one device in the device domain where the first device is located, and the first device is a core device in the device domain. The core device has the authority to control other devices in the device domain.

[0152] For example, the first device and the second device can be devices in the same device domain. Here, a device domain can be understood as a set of devices obtained by binding multiple devices that have been pre-authenticated. The bound devices will belong to only one user, so that the devices in the entire device domain trust each other, that is, cross-end control between devices in the same device domain is secure.

[0153] In this embodiment of the disclosure, the first device may be a core device in a device domain, and the second device may be a core device or a non-core device. The second device may be one or more devices in the device domain. The first device may control the second device to perform a target operation, wherein the target operation may be any operation targeting the second device, such as an unlock operation, a lock operation, a start operation, or a power-off operation.

[0154] In some embodiments, the first device may display a target component on a display interface to prompt the user to perform a target operation on other devices in the device domain. The first device may select a second device to be controlled from the other devices displayed by the target component and trigger a target operation instruction for the target component. The target operation instruction may be triggered, for example, by the user clicking a preset confirmation button. Upon receiving the target operation instruction, the first device can determine that the user needs to control the second device, and can then generate a target control instruction and send it to the second device. After receiving the target control instruction sent by the first device, the second device can perform the target operation according to the instructions of the target control instruction.

[0155] In summary, after receiving the target operation instruction, the first device in this disclosure determines the target control instruction used to instruct the second device to execute the target operation, and sends the target control instruction to the second device in the device domain where the first device is located. Since the first device and the second device in this disclosure are in the same device domain, control between two devices in the same device domain is secure. Therefore, when the first device controls the second device in its device domain to execute the target operation, no additional authentication is required, thus improving the convenience of cross-end control while ensuring its security.

[0156] In other embodiments, the target control instruction includes device authentication information of the first device, which includes an authentication result and a first device identifier of the first device. The authentication result indicates whether the first device has passed device identity authentication. One implementation of step S201 can be:

[0157] If the authentication result indicates that the first device has passed device identity authentication, and the first device is determined to be a core device in the device domain based on the first device identifier, then the target operation is executed.

[0158] For example, a user can authenticate their identity on the first device to verify whether the user using the second device is a legitimate user. Authentication methods include, but are not limited to, facial recognition, fingerprint recognition, and password authentication. Device authentication information can then be generated based on the authentication result and the first device's identifier. Furthermore, a target control instruction can be generated based on the device authentication information. The authentication result indicates whether the first device has passed device authentication, and the target control instruction instructs the second device to perform a target operation if the authentication result indicates that the first device has passed device authentication and the first device is identified as a core device based on its identifier.

[0159] It should be noted that users only need to authenticate themselves when unlocking the first device and obtain the authentication result. When the first device receives the target operation command, it does not need to repeat the authentication process. Instead, it can generate device authentication information based on the authentication result obtained when unlocking the first device, which improves the convenience of cross-device control while ensuring security.

[0160] After receiving the target control command, the second device can verify the authentication result to determine whether the second device has passed the authentication. It then searches for the first device's identifier in a third preset identifier set stored in the second device. This third preset identifier set can include the device identifiers of all core devices in the device domain where the second device resides. If the third preset identifier set includes the first device's identifier, it indicates that the first and second devices are in the same device domain, and the first device is a core device in that domain. Since the first and second devices have already undergone mutual trust authentication when bound to the same device domain, if the authentication result indicates that the first device has passed the authentication, then it can be determined that the control operation of the first device is secure, and the target operation indicated by the target control command can be executed without requiring additional authentication of the first device to verify the user's identity.

[0161] Figure 7 This is a flowchart illustrating another method for controlling a device according to an exemplary embodiment, such as... Figure 7 As shown, the device authentication information also includes security verification information, and the method may further include:

[0162] Step S202: In response to the target acquisition instruction sent by the first device, security verification information is generated. The target acquisition instruction is sent by the first device upon receiving a target operation instruction, and is used to acquire security verification information.

[0163] Step S203: Send security verification information to the first device so that the first device can generate device authentication information based on the authentication result, the first device identifier and the security verification information.

[0164] For example, a user can operate on the display interface of the first device to trigger a target operation command, whereby the target operation command can represent controlling the second device to perform the target operation. After receiving the target operation command, the first device can generate a target acquisition command and send it to the second device, whereby the target acquisition command can be used to obtain security verification information. After receiving the target acquisition command, the second device can generate security verification information and send it to the first device.

[0165] In some embodiments, the device authentication information may further include security verification information. After receiving the security verification information, the first device may generate device authentication information based on the authentication result, the first device identifier, and the security verification information.

[0166] In other embodiments, step S201 can be implemented in the following ways:

[0167] Perform security verification on the security verification information.

[0168] If the authentication result indicates that the first device has passed device identity authentication, and the first device is determined to be a core device in the device domain based on the first device identifier, and the security verification of the security verification information has passed, then the target operation indicated by the target control command is executed.

[0169] For example, while verifying the authentication result and the first device identifier, the second device can also verify the security verification information to prevent replay attacks, thereby further ensuring the security of the device authentication information sent by the first device. If the authentication result indicates that the first device has passed device identity authentication, and it is determined from the first device identifier that the first device and the second device are in the same device domain, and the security verification information has passed security verification, then the second device can determine that the control operation of the first device is secure and can execute the target operation indicated by the target control command.

[0170] In other embodiments, after generating security verification information, the second device can store the security verification information locally. After receiving the security verification information sent by the first device, it can compare the security verification information sent by the first device with the locally stored security verification information. The security verification information may include a timestamp corresponding to the generation time. If the security verification information sent by the first device is the same as the locally stored security verification information, and the timestamp indicates that the security verification information is within a valid duration, then the security verification of the security verification information can be determined to have passed. Conversely, if the security verification information sent by the first device is different from the locally stored security verification information, or the timestamp indicates that the security verification information is not within a valid duration, then the security verification of the security verification information can be determined to have failed.

[0171] In other embodiments, the device authentication information further includes a first device certificate for the first device, which is used to sign the candidate control information obtained by concatenating the authentication result, the first device identifier, and the security verification information. Step S201 can be implemented in the following way:

[0172] The first equipment certificate is legally authenticated.

[0173] If the authentication result indicates that the first device has passed device identity authentication, and the first device is determined to be a core device in the device domain based on the first device identifier, and the security verification information is verified and the first device certificate is legally authenticated, then the target operation indicated by the target control command is executed.

[0174] For example, to further ensure the security and legitimacy of the first device controlling the second device, the first device can concatenate the authentication result, the first device identifier, and the security verification information to obtain candidate control information. Then, the first device can sign the candidate control information using its first device certificate to obtain device authentication information.

[0175] After receiving the device authentication information, the second device can verify the legitimacy of the first device's certificate. If the first device's certificate passes the legitimacy verification, then the first device can be determined to be a legitimate device. If the authentication result indicates that the first device has passed device identity authentication, and the second device is determined to be in the same device domain as the first device based on the first device's identifier, and the security verification information and the first device's certificate have passed the legitimacy authentication, then the control operation of the first device can be determined to be secure, and the target operation indicated by the target control command can be executed. In this way, by verifying the device identity authentication result, the first device identifier, the security verification information, and the first device certificate, and executing the target operation indicated by the target control command only after all information has passed verification, the security and legitimacy of the first device controlling the second device can be improved.

[0176] In other embodiments, the target operation can be refused if a preset rejection condition is met. Conversely, the target operation can be executed if the preset rejection condition is not met.

[0177] The preset rejection conditions include at least one of the following: the authentication result indicates that the first device has failed device identity authentication; the first device and the second device are not in the same device domain according to the first device identifier; the security verification of the security verification information has failed; the legitimate authentication of the first device certificate has failed.

[0178] For example, if any of the authentication result, first device identifier, security verification information, or first device certificate fails verification, it indicates that the first device has a certain security risk. The second device can refuse to execute the target operation indicated by the target control command to ensure the security of the unlocking or locking operation. If the authentication result, first device identifier, security verification information, and first device certificate all pass verification, it indicates that the control of the first device is secure, and the second device can execute the target operation indicated by the target control command.

[0179] In other embodiments, the number of failures can be recorded if a preset rejection condition is met. If the number of failures exceeds a preset number, the target control command can be rejected for a preset waiting time.

[0180] For example, to prevent brute-force attacks and unforeseen security vulnerabilities, a failure count can be accumulated. The failure count can represent the number of times a preset rejection condition is met, and can include consecutive failures and / or cumulative failures. When the failure count exceeds a preset number, the response to the target control command is rejected, and the response to the target control command is resumed after a preset waiting time. This disclosure does not limit the specific rules of the failure count limiting scheme; Table 1 and...

[0181] Table 2 is for illustrative purposes only.

[0182] Number of consecutive failures 3 5 10 Waiting time 1 day 1 week permanent

[0183] Table 1

[0184] Total number of failures 5 10 20 Waiting time 1 day 1 week permanent

[0185] Table 2

[0186] Figure 8 This is a flowchart illustrating another method for controlling a device according to an exemplary embodiment, such as... Figure 8 As shown, the target operation includes an unlocking operation, and the method further includes:

[0187] Step S204: If the unlocking time exceeds the preset unlocking time, lock the second device.

[0188] For example, after the first device is unlocked by the second device, to ensure the security of the first device, if the second device is not locked by the core device within an unlocking time longer than a preset unlocking time, it can automatically relock. This embodiment does not specify a preset unlocking time for automatic locking; for example, it can be one day. The state switching of the complete solution can be as follows: Figure 9 As shown.

[0189] The following provides a specific embodiment of the process of establishing a device domain.

[0190] During the device domain setup phase, users can select any core device as the configuration entry point and then choose connectable devices from within that core device. It's important to note that users may have multiple core devices, but only one core device needs to be configured during the initial setup. For each selected device to be added to the device domain, the user can perform authentication, such as... Figure 10As shown, if authentication is successful, it proves that the user is a genuine and legitimate user of the device, allowing the device to be added to the device domain to ensure the security of subsequent global control. It should be noted that not all smart devices have authentication capabilities. Devices lacking authentication are typically those that do not require high sensitivity to the user's identity. For example, smart speakers do not need to strictly guarantee the user's identity; this is determined by the device's characteristics and functions, and therefore, such devices do not require authentication.

[0191] After user authentication is successful, the validity of certificates for all devices can be further verified to ensure that devices to be added to the device domain are manufactured by legitimate manufacturers. (Refer to...) Figure 11 Any two authenticated devices can send their public key certificates to each other for verification. Once verified, the two devices will trust and associate with each other. Devices whose certificates have passed verification can be bound to a device domain without interfering with or being interfered with by other devices. For details, refer to... Figure 12 This approach allows each core device's device identifier to be stored in every device within the device domain, ensuring that each device is bound to each core device. This enables binding of all devices within the domain, allowing subsequent unlocking or locking to only verify the stored device identifier, eliminating the need for additional identity authentication to verify the user's identity. Furthermore, it avoids assuming the user wearing the watch is the legitimate user, thus eliminating the security risk of authentication errors. By abstracting all smart devices into a unified whole with a single entry point for identity authentication, authentication no longer depends on specific devices but on the entire smart device domain, improving the convenience and security of cross-device control.

[0192] Taking the target operation as an unlocking or locking operation as an example, a specific embodiment is provided for the process of global unlocking and global locking of a device domain. Global unlocking can be understood as the core device controlling at least one other device in the device domain to unlock, and global locking can be understood as the core device controlling at least one other device in the device domain to lock.

[0193] Reference Figure 13 The full-domain unlocking can be divided into two steps: core device identity authentication and trusted token generation and verification. The core device can be the first device in this embodiment, and the other devices can be the second devices in this embodiment. The trusted token can be the device authentication information in this embodiment.

[0194] To verify that the user using the core device is a legitimate user, once the core device's authentication is successful, this core device can unlock other devices. This step replaces the user's authentication process on other devices. The core device's authentication process can be found in [reference needed]. Figure 14 For example, after a user enters initial authentication information, this information can be obfuscated using a hash algorithm. Then, the obfuscated information is verified using the encryption key HMAC_KEY. If verification is successful, an authentication result auth_result = 0 is generated; if verification fails, unlocking the core device can be refused.

[0195] The overall process of generating and verifying trusted tokens is as follows: Figure 15 As shown, a challenge can first be generated by other devices and provided to the core device to prevent replay attacks. The challenge can be security verification information in this embodiment. The challenge has a random attribute and needs to be long enough to prevent attackers from guessing it. The challenge can also have a timestamp to prevent man-in-the-middle interception and retention, ensuring the timeliness of the challenge.

[0196] The core device can concatenate the challenge provided by other devices, its own device ID, and the authentication result `auth_result`, and sign it using the device's certificate to ensure that the concatenated content comes from a legitimate device. The core device then provides the concatenated content to other devices. The device ID can be the device identifier in this embodiment. Other devices verify the concatenated content using their certificates. If verification is successful, the device proceeds to the next step; if verification fails, the device is not unlocked, and the number of failures is accumulated.

[0197] Other devices verify the challenge to ensure that it is the same as the one sent and that it is within the time limit, which can be set in seconds. If the verification is successful, proceed to the next step; if the verification fails, the device will not be unlocked and the number of failures will be accumulated.

[0198] Other devices query the device ID of the core device. If the device ID of the core device is found in the device IDs saved during the binding phase, it means that the core device and other devices have been bound together, and the next step is taken. If it is not found, it means that it has not been bound together, and the device will not be unlocked and the number of failures will be accumulated.

[0199] Other devices check the authentication result of the core device. If the authentication is successful, the device is unlocked; if the authentication fails, the device is not unlocked and the number of failures is accumulated.

[0200] Once the core devices are unlocked, all or some of the smart devices in the entire domain can be unlocked according to the user's choice. For example, PCs, mobile phones, tablets, and car infotainment systems can be unlocked, and users will no longer need to unlock them when using these devices. For some non-core devices, the corresponding smart devices, such as smart speakers, smart switches, and air conditioners, can be directly turned on.

[0201] The process of locking the entire device is similar to that of unlocking the entire device, except that the entire device will be locked instead of unlocked. For details, please refer to the process of unlocking the entire device, which will not be described here.

[0202] Figure 16 This is a block diagram illustrating a control device for a device according to an exemplary embodiment, such as... Figure 16 As shown, the device 300 may include:

[0203] The determination module 301 is configured to determine a target control instruction in response to the first device receiving a target operation instruction, wherein the target control instruction is used to instruct a second device to perform the target operation, the second device is at least one device in the device domain where the first device is located, the first device is a core device in the device domain, and the core device has the authority to control other devices in the device domain;

[0204] The sending module 302 is configured to send the target control command to the second device.

[0205] In some embodiments, the determining module 301 is configured to:

[0206] The target control instruction is determined based on the device authentication information of the first device. The device authentication information includes the authentication result and the first device identifier of the first device. The authentication result indicates whether the first device has passed device identity authentication. The target control instruction is used to instruct the second device to perform the target operation when the authentication result indicates that the first device has passed device identity authentication and the first device is determined to be a core device based on the first device identifier.

[0207] In other embodiments, the device authentication information also includes security verification information, and the determination module 302 is further configured to:

[0208] A target acquisition instruction is sent to the second device so that the second device generates security verification information upon receiving the target acquisition instruction. The target acquisition instruction is used to acquire the security verification information.

[0209] Receive security verification information sent by the second device.

[0210] Based on the authentication results, the first device identifier, and the security verification information, a target control command is generated.

[0211] In other embodiments, the device authentication information also includes a first device certificate for the first device, and the determining module 301 is configured to:

[0212] The authentication result, the first device identifier, and the security verification information are combined to obtain candidate control information.

[0213] The candidate control information is signed using the first device certificate of the first device to obtain the target control command.

[0214] In other embodiments, the sending module 302 is configured to:

[0215] Send target control commands to a second device that has authentication capabilities.

[0216] The sending module 302 is also configured as follows:

[0217] Send a preset control command to a second device that does not have authentication capabilities. The preset control command is used to control the second device that does not have authentication capabilities to perform the target operation.

[0218] Figure 17 This is a block diagram of a control device for another device according to an exemplary embodiment, such as... Figure 17 As shown, the device 300 also includes:

[0219] The acquisition module 303 is configured to acquire the second device identifier of a third device, the third device including other devices in the device domain besides the first device.

[0220] Add module 304, which is configured to add a third device to the device domain based on a first device identifier and a second device identifier.

[0221] In other embodiments, the adding module 305 is configured as follows:

[0222] The third device is authenticated based on the second device identifier to obtain the authentication result of the third device. The authentication result is determined by the third device based on the second authentication information entered by the user.

[0223] Based on the identity authentication result, the first device identifier is sent to the third device so that the third device stores the first device identifier in the first preset identifier set.

[0224] In other embodiments, the adding module 305 is configured as follows:

[0225] If the identity authentication result indicates that the third device has passed the device identity authentication, then obtain the second device certificate of the third device.

[0226] Once the second device certificate has been successfully authenticated, the first device identifier is sent to the third device.

[0227] In other embodiments, the adding module 305 is also configured to:

[0228] When the third device is the core device, the identifier of the second device is stored in the second preset identifier set of the first device.

[0229] Figure 18 This is a block diagram of a control device for another device according to an exemplary embodiment, such as... Figure 18 As shown, the device 400 may include:

[0230] The execution module 401 is configured to execute the target operation indicated by the target control instruction in response to the second device receiving the target control instruction sent by the first device. The second device is at least one device in the device domain where the first device is located, and the first device is a core device in the device domain. The core device has the authority to control other devices in the device domain.

[0231] In other embodiments, the target control instruction includes device authentication information of the first device, which includes authentication result and a first device identifier of the first device. The authentication result indicates whether the first device has passed device identity authentication. Execution module 401 is configured to:

[0232] If the authentication result indicates that the first device has passed device identity authentication, and the first device is determined to be a core device in the device domain based on the first device identifier, then the target operation is executed.

[0233] Figure 19 This is a block diagram of a control device for another device according to an exemplary embodiment, such as... Figure 19 As shown, the device 400 may further include:

[0234] The generation module 402 is configured to generate security verification information in response to a target acquisition command sent by the first device. The target acquisition command is sent by the first device upon receiving a target operation command, and is used to acquire the security verification information.

[0235] The sending module 403 is configured to send security verification information to the first device so that the first device can generate device authentication information based on the authentication result, the first device identifier and the security verification information.

[0236] In other embodiments, execution module 401 may be configured to:

[0237] Perform security verification on the security verification information.

[0238] If the authentication result indicates that the first device has passed device identity authentication, and the first device is determined to be a core device in the device domain based on the first device identifier, and the security verification of the security verification information has passed, then the target operation indicated by the target control command is executed.

[0239] In other embodiments, the device authentication information also includes a first device certificate for the first device, which is used to sign the candidate control information obtained by concatenating the authentication result, the first device identifier, and the security verification information. The execution module 401 can be configured to:

[0240] The first equipment certificate is legally authenticated.

[0241] If the authentication result indicates that the first device has passed device identity authentication, and the first device is determined to be a core device in the device domain based on the first device identifier, and the security verification information is verified and the first device certificate is legally authenticated, then the target operation indicated by the target control command is executed.

[0242] Figure 20 This is a block diagram of a control device for another device according to an exemplary embodiment, such as... Figure 20 As shown, the device 400 may further include:

[0243] Reject module 404 is configured to refuse to execute the target operation if a preset rejection condition is met.

[0244] Accordingly, the execution module 401 is configured to perform the target operation if the preset rejection conditions are not met.

[0245] The preset rejection conditions include at least one of the following:

[0246] The authentication result indicates that the first device failed the device identity authentication.

[0247] Based on the first device identifier, it is determined that the first device and the second device are not in the same device domain.

[0248] Security verification of security information failed.

[0249] The first device certificate failed to be valid.

[0250] In other embodiments, the rejection module 404 is also configured to:

[0251] If the preset rejection conditions are met, record the number of failures.

[0252] If the number of failures exceeds the preset number, the target control command will be refused for a preset waiting time.

[0253] In other embodiments, execution module 401 is configured to:

[0254] If the first device identifier is included in the third preset identifier set stored in the second device, the first device is determined to be a core device in the device domain.

[0255] In other embodiments, the execution module 401 is also configured to

[0256] If the unlock duration exceeds the preset unlock duration, the second device will be locked.

[0257] This disclosure also provides a computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, implement the steps of the control method for the device provided in this disclosure.

[0258] Figure 21 This is a block diagram illustrating an electronic device according to an exemplary embodiment. For example, the electronic device 500 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0259] Reference Figure 21 The electronic device 500 may include one or more of the following components: processing component 502, memory 504, power supply component 506, multimedia component 508, audio component 510, input / output interface 512, sensor component 514, and communication component 516.

[0260] Processing component 502 typically controls the overall operation of electronic device 500, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 502 may include one or more processors 520 to execute instructions to complete all or part of the steps of the device control method described above. Furthermore, processing component 502 may include one or more modules to facilitate interaction between processing component 502 and other components. For example, processing component 502 may include a multimedia module to facilitate interaction between multimedia component 508 and processing component 502.

[0261] Memory 504 is configured to store various types of data to support the operation of electronic device 500. Examples of such data include instructions for any application or method operating on electronic device 500, contact data, phonebook data, messages, pictures, videos, etc. Memory 504 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0262] Power supply component 506 provides power to various components of electronic device 500. Power supply component 506 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 500.

[0263] Multimedia component 508 includes a screen that provides an output interface between the electronic device 500 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 508 includes a front-facing camera and / or a rear-facing camera. When the electronic device 500 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0264] Audio component 510 is configured to output and / or input audio signals. For example, audio component 510 includes a microphone (MIC) configured to receive external audio signals when electronic device 500 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 504 or transmitted via communication component 516. In some embodiments, audio component 510 also includes a speaker for outputting audio signals.

[0265] Input / output interface 512 provides an interface between processing component 502 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, start buttons, and lock buttons.

[0266] Sensor assembly 514 includes one or more sensors for providing state assessments of various aspects of electronic device 500. For example, sensor assembly 514 may detect the on / off state of electronic device 500, the relative positioning of components such as the display and keypad of electronic device 500, changes in position of electronic device 500 or a component of electronic device 500, the presence or absence of user contact with electronic device 500, orientation or acceleration / deceleration of electronic device 500, and temperature changes of electronic device 500. Sensor assembly 514 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 514 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 514 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0267] Communication component 516 is configured to facilitate wired or wireless communication between electronic device 500 and other devices. Electronic device 500 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 516 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 516 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0268] In an exemplary embodiment, the electronic device 500 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the control method of the device.

[0269] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 504 including instructions, which can be executed by a processor 520 of an electronic device 500 to perform the control method of the device. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0270] In another exemplary embodiment, a computer program product is also provided, which includes a computer program executable by a programmable electronic device, the computer program having a code portion for performing the control method of the device described above when executed by the programmable electronic device.

[0271] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0272] It should be understood that, unless otherwise specifically indicated, features of various embodiments of this disclosure described herein can be combined with each other. As used herein, the term “and / or” includes any one of the relevant listed items and any combination of any two or more; similarly, “at least one of…” includes any one of the relevant listed items and any combination of any two or more.

[0273] Furthermore, the term "above" as used herein with respect to components, elements, or material layers formed or located "above" a surface may be used to indicate that the component, element, or material layer is "indirectly" positioned (e.g., placed, formed, deposited, etc.) on the surface such that one or more additional components, elements, or layers are arranged between the surface and the component, element, or material layer. However, the term "above" as used with respect to components, elements, or material layers formed or located "above" a surface may also optionally have a specific meaning: that the component, element, or material layer is "directly" positioned (e.g., placed, formed, deposited, etc.) on the surface, for example, in direct contact with the surface.

[0274] Although terms such as “first,” “second,” and “third” may be used herein to describe various components, parts, regions, layers, or sections, these components, parts, regions, layers, or sections are not limited to these terms. Rather, these terms are used only to distinguish one component, part, region, layer, or section from another. Therefore, without departing from the teachings of the examples described herein, the first component, part, region, layer, or section mentioned in the examples may also be referred to as the second component, part, region, layer, or section. Furthermore, the terms “first” and “second” are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as “first” or “second” may explicitly or implicitly include at least one of that feature. In the description herein, “a plurality” means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0275] Furthermore, the term “exemplary” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as advantageous compared to other aspects or designs. Rather, the use of the term “exemplary” is intended to present the concept in a concrete manner. As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless otherwise specified or clear from the context, “X applies A or B” is intended to mean any of the natural inclusive arrangements. That is, “X applies A or B” satisfies any of the foregoing instances if X applies A; X applies B; or both X applies A and B. Additionally, unless otherwise specified or clear from the context to refer to the singular form, the articles “a” and “an” as used in this application and the appended claims are generally understood to mean “one or more.”

[0276] Similarly, although this disclosure has been shown and described with respect to one or more implementations, equivalent variations and modifications will occur to those skilled in the art upon reading and understanding the specification and drawings. This disclosure includes all such modifications and variations and is limited only by the scope of the claims. In particular, with respect to the various functions performed by the components described above (e.g., elements, resources, etc.), unless otherwise indicated, the terminology used to describe such components is intended to correspond to any component (functionally equivalent) that performs the specific function of the described component, even if structurally not equivalent to the disclosed structure. Furthermore, although specific features of this disclosure may have been disclosed with respect to only one of several implementations, such features may be combined with one or more other features of other implementations, as may be desired and advantageous to any given or particular application. Moreover, with regard to the terms “comprising,” “owning,” “having,” “having,” or variations thereof as used in the detailed description or claims, such terms are intended to be inclusive in a manner similar to the term “including.”

[0277] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the appended claims.

[0278] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A method for controlling a device, characterized in that, The method includes: In response to the first device receiving a target operation instruction, a target control instruction is determined, wherein the target control instruction is used to instruct a second device to perform the target operation, the second device is at least one device in the device domain where the first device is located, the first device is a core device in the device domain, and the core device has the authority to control other devices in the device domain; Send the target control command to the second device.

2. The method according to claim 1, characterized in that, The target determination control command includes: The target control instruction is determined based on the device authentication information of the first device, wherein the device authentication information includes an authentication result and a first device identifier of the first device, the authentication result indicating whether the first device has passed device identity authentication, and the target control instruction is used to instruct the second device to perform the target operation when the authentication result indicates that the first device has passed device identity authentication and the first device identifier indicates that the first device is a core device.

3. The method according to claim 2, characterized in that, The device authentication information also includes security verification information, and determining the target control command based on the device authentication information of the first device includes: Send a target acquisition instruction to the second device, so that the second device generates security verification information upon receiving the target acquisition instruction, wherein the target acquisition instruction is used to acquire the security verification information; Receive the security verification information sent by the second device; The target control command is generated based on the authentication result, the first device identifier, and the security verification information.

4. The method according to claim 3, characterized in that, The device authentication information also includes the first device certificate of the first device, and the step of generating the target control command based on the authentication result, the first device identifier, and the security verification information includes: The authentication result, the first device identifier, and the security verification information are concatenated to obtain candidate control information; The candidate control information is signed using the first device certificate of the first device to obtain the target control command.

5. The method according to claim 1, characterized in that, Sending the target control command to the second device includes: Send the target control command to the second device that has identity authentication function; The method further includes: A preset control command is sent to the second device, which does not have an authentication function, and the preset control command is used to control the second device, which does not have an authentication function, to perform the target operation.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Obtain the second device identifier of the third device, wherein the third device includes other devices in the device domain besides the first device; The third device is added to the device domain based on the first device identifier and the second device identifier.

7. The method according to claim 6, characterized in that, Adding the third device to the device domain based on the first device identifier and the second device identifier includes: The third device is authenticated based on the second device identifier to obtain the authentication result of the third device. The authentication result is determined by the third device based on the second authentication information input by the user. Based on the identity authentication result, the first device identifier is sent to the third device so that the third device stores the first device identifier in the first preset identifier set.

8. The method according to claim 7, characterized in that, Sending the first device identifier to the third device based on the authentication result includes: If the identity authentication result indicates that the third device has passed device identity authentication, obtain the second device certificate of the third device; If the second device certificate is successfully authenticated, the first device identifier is sent to the third device.

9. The method according to claim 8, characterized in that, Adding the third device to the device domain based on the first device identifier and the second device identifier further includes: In the case where the third device is a core device, the second device identifier is stored in the second preset identifier set of the first device.

10. A method for controlling a device, characterized in that, The method includes: In response to receiving a target control command from a first device, the second device executes the target operation indicated by the target control command, wherein the second device is at least one device in the device domain in which the first device is located, the first device is a core device in the device domain, and the core device has the authority to control other devices in the device domain.

11. The method according to claim 10, characterized in that, The target control command includes device authentication information of the first device, the device authentication information includes authentication result and first device identifier of the first device, and the authentication result indicates whether the first device has passed device identity authentication; The target operation indicated by the target control command includes: The target operation is performed when the authentication result indicates that the first device has passed device identity authentication and the first device is determined to be a core device in the device domain based on the first device identifier.

12. The method according to claim 11, characterized in that, The device authentication information also includes security verification information; the method further includes: In response to a target acquisition instruction sent by the first device, the security verification information is generated; the target acquisition instruction is sent by the first device upon receiving the target operation instruction, and the target acquisition instruction is used to acquire the security verification information. The security verification information is sent to the first device so that the first device generates the device authentication information based on the authentication result, the first device identifier, and the security verification information.

13. The method according to claim 12, characterized in that, The target operation indicated by the target control command includes: The security verification information is then subjected to security verification. If the authentication result indicates that the first device has passed device identity authentication, and the first device is determined to be a core device in the device domain based on the first device identifier, and the security verification of the security verification information has passed, then the target operation indicated by the target control command is executed.

14. The method according to claim 13, characterized in that, The device authentication information also includes a first device certificate of the first device, which is used to sign the candidate control information obtained by splicing the authentication result, the first device identifier and the security verification information. The target operation indicated by the target control command includes: Perform legal authentication on the first device certificate; If the authentication result indicates that the first device has passed device identity authentication, and the first device is determined to be a core device in the device domain based on the first device identifier, and the security verification information is verified and the first device certificate is legally authenticated, then the target operation indicated by the target control command is executed.

15. The method according to claim 14, characterized in that, The method further includes: If the preset rejection conditions are met, the target operation will not be executed. The target operation indicated by the target control command includes: If the preset rejection condition is not met, the target operation is performed; The preset rejection condition includes at least one of the following: The authentication result indicates that the first device failed device identity authentication; Based on the first device identifier, it is determined that the first device and the second device are not in the same device domain; The security verification of the security verification information failed. The authentication of the first device certificate failed.

16. The method according to claim 15, characterized in that, The method further includes: If the preset rejection condition is met, record the number of failures; If the number of failures exceeds a preset number, the target control command will be refused to be responded to within a preset waiting time.

17. The method according to claim 11, characterized in that, The step of determining the first device as a core device in the device domain based on the first device identifier includes: If the first device identifier is included in the third preset identifier set stored in the second device, the first device is determined to be a core device in the device domain.

18. The method according to any one of claims 10-17, characterized in that, The target operation includes an unlocking operation, and the method further includes: If the unlocking time exceeds the preset unlocking time, the second device is locked.

19. A control device for an equipment, characterized in that, The device includes: The determination module is configured to determine a target control instruction in response to a first device receiving a target operation instruction, wherein the target control instruction is used to instruct a second device to perform the target operation, the second device is at least one device in the device domain where the first device is located, the first device is a core device in the device domain, and the core device has the authority to control other devices in the device domain; The sending module is configured to send the target control command to the second device.

20. A control device for an equipment, characterized in that, The device includes: The execution module is configured to execute the target operation indicated by the target control instruction in response to the second device receiving a target control instruction sent by the first device, wherein the second device is at least one device in the device domain in which the first device is located, the first device is a core device in the device domain, and the core device has the authority to control other devices in the device domain.

21. An electronic device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to execute the computer program in the memory to implement the steps of the method according to any one of claims 1-9 or 10-18.

22. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the method described in any one of claims 1-9 or 10-18.

23. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1-9 or 10-18.

Images