Equipment management method, electronic equipment and storage medium

Abstract

The invention discloses a device management method, an electronic device and a storage medium, and the method comprises the steps that a first device obtains first associated information corresponding to the first device and obtains second associated information corresponding to a second device, the first associated information and the second associated information respectively comprise a user identifier of an associated user of the corresponding equipment and an operation authority of the associated user of the corresponding equipment to the corresponding equipment; based on the first association information and the second association information, determining a credible authority between the first device and the second device, the credible authority being an operation authority of a common association user of the first device and the second device to both the first device and the second device; and allowing the second device to perform an operation corresponding to the trusted permission on the first device. By means of the method, the safety of operation between the devices can be improved.

Description

Technical Field

[0001] The present application relates to the field of intelligent control technology for the Internet of Things, and in particular to a device management method, an electronic device, and a storage medium. Background Art

[0002] The IoT intelligent control technology can realize data interaction and cross-device operation between devices. However, although the existing IoT intelligent control technology can realize data interaction or cross-device operation between devices, the security of data interaction and other operations between devices is still insufficient. Therefore, how to ensure the security of operations between devices is a topic that needs to be studied urgently. Summary of the invention

[0003] The main technical problem solved by the present application is to provide a device management method, an electronic device and a storage medium, which can improve the security of operations between devices.

[0004] To solve the above technical problems, a technical solution adopted in the present application is: to provide a device management method, the method comprising: a first device obtains first associated information corresponding to itself, wherein the first associated information includes a first user identifier of an associated user of the first device, and the operating authority of the associated user of the first device over the first device; obtains second associated information corresponding to a second device, wherein the second associated information includes a second user identifier of an associated user of the second device, and the operating authority of the associated user of the second device over the second device; based on the first associated information and the second associated information, determines a trusted authority between the first device and the second device, wherein the trusted authority is the operating authority that the common associated user of the first device and the second device has over both the first device and the second device; and allows the second device to perform operations corresponding to the trusted authority on the first device.

[0005] To solve the above technical problems, another technical solution adopted by the present application is: to provide a device management method, the method comprising: determining the association relationship between the user and the device, and the user's operating authority over the device based on the association indication sent by the client; generating device association information, wherein the association information includes the user identifier of the device's associated user, and the associated user's operating authority over the device; sending the association information to the device, wherein different devices allow each other to perform operations corresponding to the trusted authority when it is determined based on the association information that there is a trusted authority, wherein the trusted authority is the operating authority that the associated user of different devices has for different devices.

[0006] To solve the above technical problems, another technical solution adopted in the present application is: to provide an electronic device, including a memory and a processor, the memory stores program instructions, and the processor is used to execute the program instructions to implement the above device management method.

[0007] In order to solve the above technical problems, another technical solution adopted by the present application is: providing a computer-readable storage medium, which is used to store program instructions, and the program instructions can be executed to implement the above device management method.

[0008] In the above scheme, the first device obtains the first association information corresponding to itself and the second association information corresponding to the second device, and determines the trusted authority between the first device and the second device based on the first association information and the second association information, thereby allowing the second device to perform operations corresponding to the trusted authority on the first device. In this process, the first association information and the second association information contain the associated user information and the corresponding operation authority corresponding to the device. By selecting the common operation authority of the common associated user of the first device and the second device as the trusted authority between the first device and the second device, the operations between the first device and the second device other than the trusted authority are restricted, thereby improving the security of operations between devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 It is a flowchart of an embodiment of a device management method provided by the present application;

[0010] Figure 2 This is a schematic diagram of a trusted authority verification rule provided by this application;

[0011] Figure 3 It is a flowchart of another embodiment of the device management method provided by the present application;

[0012] Figure 4 It is a flowchart of a specific embodiment of the device management method provided by this application;

[0013] Figure 5 It is a flowchart of another specific embodiment of the device management method provided by the present application;

[0014] Figure 6 It is a flowchart of an embodiment of the device management device of the present application;

[0015] Figure 7 It is a schematic diagram of the framework of an embodiment of the electronic device of the present application;

[0016] Figure 8 It is a schematic diagram of a framework of an embodiment of a computer-readable storage medium of the present application. DETAILED DESCRIPTION

[0017] In order to make the purpose, technical solution and effect of the present application clearer and more specific, the present application is further described in detail below with reference to the accompanying drawings and examples.

[0018] It should be noted that the terms "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. The term "and / or" is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the previously associated objects are in an "or" relationship. In addition, the term "at least one" in this article represents any combination of at least two of any one or more of a plurality of types. For example, at least one of A, B, and C can represent any one or more elements selected from the set consisting of A, B, and C.

[0019] See also Figure 1 , Figure 1 It is a flow chart of an embodiment of the device management method provided by the present application. It should be noted that if there are substantially the same results, this embodiment does not take Figure 1 The process sequence shown is limited. Figure 1 As shown, this embodiment includes:

[0020] Step S11: The first device obtains first association information corresponding to itself.

[0021] The first association information includes a first user identifier of an associated user of the first device and an operation authority of the associated user of the first device on the first device;

[0022] The associated user in this embodiment refers to a user who has an associated relationship with the first device, and users with different associated relationships may have different operation permissions corresponding to the first device. In one embodiment, the type of the associated user includes at least one of a shared user and a bound user, wherein the shared user has some or all of the operation permissions, and the bound user has all of the operation permissions.

[0023] In a specific implementation, the bound users in the associated users may specifically include the belonging user and the family user, wherein the belonging user refers to the user directly bound to the first device, and the family user refers to the user who is invited by the belonging user to enter the family and thus obtains the right to use the first device. The shared user in the associated users refers to the user who is shared by the belonging user and thus obtains part or all of the operation rights of the first device. Among them, the belonging user and the family user both have all the operation rights of the first device, and the shared user has part or all of the shared operation rights.

[0024] The first user identifier in this embodiment can uniquely represent the associated user. Specifically, the first user identifier can be a first user serial number, a first user email, or a first user unique identifier, etc. In one embodiment, the first user identifier is a first user serial number. For example, multiple user information such as the registration time, region type, and user type of the associated user can be combined and encrypted to generate a first user serial number corresponding to the associated user, so that one first user identifier corresponds to only one associated user.

[0025] The first device may obtain the first associated information corresponding to itself from the local device or the cloud platform. The first associated information corresponding to the first device itself and stored locally on the device is actually obtained and stored in advance from the cloud platform. In one embodiment, the first device may obtain the encrypted associated information stored locally on the device or in the cloud platform to ensure the integrity and security of the first associated information during transmission, wherein the encrypted associated information refers to the first associated information encrypted by the cloud platform. When the encrypted associated information is obtained, the first device may decrypt the encrypted associated information, thereby obtaining the first associated information completely and securely.

[0026] The locally stored encrypted association information may be updated by overwriting or deleting. The encrypted association information may include a first trusted code. In one embodiment, the locally stored encrypted association information is updated by deleting. For example, when the encrypted association information changes or it is determined that the first device is no longer associated with the associated user, the locally stored encrypted association information is cleared, and further, the locally stored first association information is cleared. Obtaining the encrypted association information sent by the cloud platform to update the locally stored encrypted association information can be understood as updating the locally stored first association information.

[0027] In a specific implementation, step S11 further includes: based on the association change notification sent by the cloud platform, determining that the first device is to be disassociated from its associated user, and clearing the first association information stored locally.

[0028] The encrypted association information may include a first trusted code, and the first device may obtain the encrypted association information in the cloud platform and decrypt it to obtain the corresponding first association information. In one embodiment, step S11 includes: obtaining a first trusted code from the cloud platform, where the first trusted code is generated by the cloud platform based on the first association information of the first device. Decrypting the first trusted code obtains the first association information.

[0029] The first credible code can be obtained by encrypting the first associated information through at least one of algorithm encryption, end-to-end encryption, and encryption factor. In one embodiment, the first credible code is obtained by the cloud platform encrypting the first associated information using the encryption factor of the first device.

[0030] In the process of decrypting the first trusted code and obtaining the first associated information, there may be a decryption method corresponding to the algorithm encryption, end-to-end encryption, and encryption factor, and the first trusted code is decrypted to obtain the corresponding first associated information. In one embodiment, a decryption factor corresponding to the encryption factor may be obtained, wherein the decryption factor may be actively obtained by the first device from the cloud platform, or the decryption factor sent by the cloud platform may be passively received. In a specific embodiment, step S11 further includes: obtaining a decryption factor corresponding to the encryption factor sent by the cloud platform.

[0031] In a specific implementation, decrypting the first trusted code to obtain the first associated information includes: decrypting the first trusted code using a decryption factor to obtain the first associated information.

[0032] The first device may actively or passively receive the first trusted code sent by the cloud platform. For example, the first device may actively initiate a request to the cloud platform to obtain the first trusted code sent by the cloud platform. Alternatively, the first device passively receives the first trusted code sent by the cloud platform. In one embodiment, the first device may obtain the first trusted code corresponding to itself sent by the cloud platform by sending a first trusted code synchronization request to the cloud platform.

[0033] In a specific embodiment, a first trusted code synchronization request is sent to a cloud platform to obtain a first trusted code corresponding to itself and sent by the cloud platform, including: in response to the first device currently satisfying any synchronization condition, a trusted code synchronization request is sent to the cloud platform, wherein the synchronization condition includes at least one of the following: receiving an association change notification sent by the cloud platform, switching from an offline state to an online state, receiving an access control request from a second device and the first trusted code does not exist locally, receiving an access control request from a second device and the first trusted code locally has expired, the association change notification is sent by the cloud platform at the request of an associated user of the first device, or an associated user of the first device to change the operating authority of the first device, and the validity period of the first trusted code is determined based on the valid timestamp when the first association information includes a valid period timestamp; receiving the first trusted code sent by the cloud platform in response to the trusted code synchronization request.

[0034] In another embodiment, when the first association information includes a validity period timestamp, step S11 further includes: determining that the first trusted code has expired, and clearing the first association relationship stored locally.

[0035] In a specific implementation, the effective time of the effective time stamp may be compared with the real time to determine whether the first association information is valid. For example, if the effective time is after the real time, the first association information is valid.

[0036] Step S12: Acquire second association information corresponding to the second device.

[0037] The second association information includes a second user identifier of a user associated with the second device and operation authority of the user associated with the second device on the second device.

[0038] The second user identifier and the second device acquire the second associated information corresponding to the second device in the same manner as the aforementioned process of the first user identifier and the first device acquiring the first associated information, so reference may be made to the relevant description of step S11.

[0039] The first device may directly or indirectly obtain the second associated information of the second device. For example, directly receive the second associated information or encrypted associated information sent by the second device to directly or indirectly obtain the corresponding second associated information through decryption. In one embodiment, step S12 includes: receiving the second associated information sent by the second device; or, receiving the second trusted code sent by the second device, wherein the second trusted code is generated by the cloud platform based on the second associated information; decrypting the second trusted code to obtain the second associated information. For example, obtain the encrypted second trusted code sent by the second device from the cloud platform, obtain the decryption factor corresponding to the second device, decrypt the second trusted code based on the decryption factor corresponding to the second device, and obtain the second associated information corresponding to the second device. Alternatively, directly receive the second associated information sent by the second device.

[0040] Step S13: Determine the trusted authority between the first device and the second device based on the first association information and the second association information.

[0041] The trusted authority is the operation authority that a common associated user of the first device and the second device has on both the first device and the second device.

[0042] It is understandable that the operation permissions of the common associated user on the first device and the operation permissions on the second device can be obtained separately, and the trusted permissions between the first device and the second device can be determined through judgment rules. In one embodiment, the judgment rules can be formulated based on the association relationship between the device and the associated user and the permission dimension of the operation permissions, so as to realize the judgment of the device trusted permission operation scenarios under different device association information, thereby realizing the security of trusted permission operations between devices. Furthermore, while the devices within the trusted permission range of the associated user are performing corresponding operations, it is effectively reduced that the operations of other associated users that are not allowed to be executed or the shared data that is not allowed to be obtained are effectively reduced.

[0043] In one embodiment, step S13 includes: comparing the first user identifier and the second user identifier to determine whether the first device and the second device have a common associated user; in response to the existence of a common associated user, obtaining the first operating permission of the common associated user for the first device, and the second operating permission of the common associated user for the second device; obtaining the intersection of the first operating permission and the second operating permission as a trusted permission.

[0044] In a specific embodiment, the situation where there is a common associated user may be at least one of a common binding user and a common sharing user. Among them, the priority of the binding user is higher than that of the sharing user. For example, in the case where there is a common binding user and a common sharing user, it can be understood that there is a common binding user. In the case where there is a common binding user, the intersection of all operation permissions of the binding user in the first device and all operation permissions of the common binding user in the second device is used as a trusted permission. In the case where there is no common binding user and there is a common sharing user, the intersection of the operation permissions of the sharing user in the first device and the operation permissions of the common sharing user in the second device is used as a trusted permission. That is, it is understood that when there is a common binding user, the sharing user corresponding to the first device and the sharing user of the second device are the same or different, all operation permissions are credible. In the case where there is no common binding user and there is a common sharing user, the operation permissions of the first device and the operation permissions of the second device shared by the sharing users are credible.

[0045] See also Figure 2 , Figure 2It is a schematic diagram of a trusted permission verification rule provided by the present application. Among them, associated users include bound users and shared users, wherein the permission set refers to the operating permission set of the shared user, and the total set of trusted permissions is all trusted permission operations between the first device and the second device. In the case of a common bound user, all operating permissions are trustworthy. In the absence of a common bound user, there is a common shared user, and the permission set is included in the total set of trusted permissions, the intersection of the operating permission set corresponding to the common shared user and the first device and the operating permission set corresponding to the second device, the permission operations in the intersection are trusted permissions. For example, the total set of trusted permissions is {P1, P2, P3, P4}, the permission set of the shared user in the first device is {P1, P2}, the permission set of the shared user in the second device is {P1, P3}, the bound users of the first device and the second device are different, and the shared users are the same, then {P1} in device A and device B is a trusted permission. The permission set of the shared user in the first device is {P1, P2}, the permission set of the shared user in the second device is {P1, P3}, and the bound users of the first device and the second device are the same, then {P1, P2, P3, P4} in device A and device B are trusted permissions.

[0046] Step S14: allowing the second device to perform operations corresponding to the trusted authority on the first device.

[0047] In one implementation, the second device is allowed to perform an operation corresponding to the trusted authority on the first device, which is a permission operation included in the trusted authority.

[0048] In this embodiment, the first device obtains the first association information corresponding to itself and the second association information corresponding to the second device, and determines the trusted authority between the first device and the second device based on the first association information and the second association information, thereby allowing the second device to perform operations corresponding to the trusted authority on the first device. In this process, the first association information and the second association information contain the associated user information and the corresponding operation authority corresponding to the device. By selecting the common operation authority of the common associated user of the first device and the second device as the trusted authority between the first device and the second device, the operations between the first device and the second device other than the trusted authority are restricted, thereby improving the security of operations between devices.

[0049] See also Figure 3 , Figure 3 It is a flow chart of another embodiment of the device management method provided by the present application. It should be noted that if there are substantially the same results, this embodiment does not take Figure 3 The process sequence shown is limited. Figure 3 As shown, this embodiment includes:

[0050] Step S31: Based on the association indication sent by the client, determine the association relationship between the user and the device, and the user's operation authority for the device.

[0051] Users can establish a relationship between users and devices by binding with devices on the client, sharing, and inviting other users to join the family. The relationship between users and devices can also be cancelled by unbinding, canceling sharing, transferring devices, etc. Among them, users who establish a binding with the device have all operating permissions, users who establish a relationship with the device through invitation have all operating permissions, and users who establish a relationship with the device through sharing have some or all operating permissions. In the case of any of the above-mentioned establishment or termination of a relationship, the association between the user and the device changes, and the cloud platform receives the association instruction sent by the client.

[0052] In one embodiment, the association indication sent by the client may be in the form of a signal to notify the cloud platform to perform corresponding updates of the user and the device. Based on the association indication sent by the client, the association relationship between the user and the device and the user's operation authority over the device are obtained from the client. In one embodiment, the association relationship between the user and the device can be understood as the association relationship between user information and device information, and user information, device information and corresponding association information between the user and the device can be obtained in the association relationship between the user and the device.

[0053] In another embodiment, the association indication is an association relationship establishment indication or an association relationship change indication. Before step S11, the method further includes: receiving an association change indication sent by the client; in response to the relationship change indication being an association relationship removal indication, clearing the locally stored trusted code of the device; in response to the relationship change indication being an association relationship establishment indication or an association relationship change indication, executing the association indication sent by the client to determine the association relationship between the user and the device, and the user's operation authority over the device.

[0054] Step S32: Generate association information of the device, wherein the association information includes a user identifier of an associated user of the device and the associated user's operation authority over the device.

[0055] In one embodiment, the type of associated users includes at least one of a shared user and a bound user, the bound user has all operation permissions, and the shared user has part or all of the operation permissions.

[0056] In the case where there is an association relationship between a user and a device, the user is an associated user. The cloud platform can obtain the corresponding user identifier from the association relationship between the user and the device determined in the client. Among them, the specific description of the associated user can refer to the relevant description in step S11. In one embodiment, user information that can be used to characterize the accurate associated user is obtained from the user information as the user identifier. The user identifier can be a user serial number, a user email, or a user unique identifier. The specific description of the user identifier can refer to the relevant description of the first user identifier in step S11.

[0057] The associated information may also include information for determining whether the associated information is valid, so as to verify the validity of the associated information. Whether the information is valid may be determined by time verification, source verification, content verification or technical verification. For example, whether the information is valid may be determined by a timestamp or timeliness check, so as to verify the validity of the associated information in terms of time verification. In a specific embodiment, the associated information also includes a validity period timestamp of the associated information. By comparing the valid timestamp with the real time, it is determined whether the associated information is valid. For example, when the valid timestamp is after the real time, the associated information is valid.

[0058] Step S33: Sending association information to the device.

[0059] Among them, when different devices determine that there is a trusted authority based on the association information, the other party is allowed to perform operations corresponding to the trusted authority. The trusted authority is the operation authority that the associated user of different devices has for different devices.

[0060] The association information sent to the device may be encrypted association information, and the specific description of the encrypted association information may refer to the relevant description in step S11. In one embodiment, step S33 includes: encrypting the association information using an encryption factor to obtain a trusted code.

[0061] In a specific implementation, a decryption factor corresponding to the encryption factor may also be sent to decrypt the associated information. Specifically, step S33 includes: encrypting the associated information using the encryption factor of the device to obtain a trusted code of the device. Sending the trusted code and the decryption factor corresponding to the encryption factor to the device.

[0062] The encryption factor in this article can be generated based on device information and random encryption information. The device information contains information that can be used to characterize and distinguish different devices. For example, the device information contains at least one of the unique identifier, unique serial number, and device ID of the device. The random encryption information can generate a segment of characters through an algorithm. For example, a specific number of digits of characters are generated in the device dimension through an algorithm. In a specific embodiment, before the associated information is encrypted using the encryption factor of the device to obtain the trusted code of the device, it also includes: using the device identification of the device and a specific number of digits of random characters to generate the encryption factor of the device. For example, the encryption factor of the device is generated using the device identification of the device and random six-digit characters.

[0063] See also Figure 4 , Figure 4 This is a flow chart of a specific embodiment of the device management method provided by this application. Figure 4 As shown, the device management method provided in this embodiment may include the following steps:

[0064] Step S41: The first device receives the access control request sent by the second device. Step S42: Determine whether the first trusted code exists locally on the first device. If the judgment result of step S42 is yes, execute step S43 to decrypt the first trusted code. Execute step S44 to determine whether the first device has an expired first trusted code locally. If the judgment result of step S44 is no, execute step S45 to determine whether the first device and the second device have the same bound user. If the judgment result of step S45 is no, execute step S46 to determine whether the first device and the second device have the same shared user. If the judgment result of step S46 is yes, execute step S47 to determine whether the operation performed by the second device on the first device is within the trusted authority. If the judgment result of step S45 or step S47 is yes, execute step S48 to allow the second device to operate on the first device to perform corresponding access control. If the judgment result of step S46 or step S47 is no, execute step S49 to not allow the second device to operate on the first device and terminate the access control. In step S410, the cloud platform receives an association change notification, or in step S411, the first device changes from an offline state to an online state, or in step S42, the judgment result is no, or in step S44, the first device sends a trusted code synchronization request in step S412. In step S413, the cloud platform determines whether there is an associated user in the first device. In step S413, the cloud platform matches the first trusted code and the corresponding decryption factor in step S414, and in step S415, the cloud platform synchronizes the first trusted code and the decryption factor to the first device. In step S413, the cloud platform sends a signal to the first device that there is no first trusted code in step S416.

[0065] See also Figure 5 , Figure 5 FIG. 1 is a flow chart of another specific embodiment of the device management method provided by the present application. Figure 5 As shown, the device management method provided in this embodiment may include the following steps:

[0066] Step S51: The cloud platform responds to the change in the user-device relationship status. Step S52: The cloud platform determines whether the associated user and the device are unbound. If the judgment result of step S52 is no, execute step S53 to update and save the association information corresponding to the device. Execute step S54 to determine whether there is an encryption factor corresponding to the device in the cloud platform. If the judgment result of step S54 is no, execute step S55 to generate an encryption factor corresponding to the device. Execute step S56 to store the encryption factor corresponding to the device. If the judgment result of step S54 is yes or after executing step S56 to store the encryption factor, execute step S57 to calculate and generate a trusted code using the encryption factor and the associated information. Execute step S58 to store the trusted code in the cloud platform. If the judgment result of step S52 is yes, execute step S59 to clear the trusted code corresponding to the storage device. After executing step S58 or step S510, execute step S510 to send an association change notification to the device.

[0067] In some application scenarios, the device management method provided in this application can be applied to the field of intelligent control technology of the Internet of Things, etc. The execution subject for implementing the device management method described in this application can be a device management device, an electronic device, etc. For example, the device management device can be set in a terminal device or a server or other processing device, wherein the terminal device can be an audio device, an electronic device, a device (User Equipment, UE), a handheld device, a computing device, a vehicle-mounted device, a wearable device, etc. In some possible implementations, the device management method can be implemented by a processor calling a computer-readable instruction stored in a memory.

[0068] See also Figure 6 , Figure 6It is a flow chart of an embodiment of the device management device of the present application. The device management device 600 includes a first association information acquisition module 610, a second association information acquisition module 620, a trusted authority acquisition module 630, an operation module 640, an information determination module 650, an association information generation module 660, and an association information sending module 670. The first association information acquisition module 610 is used for the first device to acquire the first association information corresponding to itself, wherein the first association information includes the first user identifier of the associated user of the first device, and the operation authority of the associated user of the first device to the first device. The second association information acquisition module 620 is used to acquire the second association information corresponding to the second device, wherein the second association information includes the second user identifier of the associated user of the second device, and the operation authority of the associated user of the second device to the second device. The trusted authority acquisition module 630 is used to determine the trusted authority between the first device and the second device based on the first association information and the second association information, wherein the trusted authority is the operation authority that the common associated user of the first device and the second device has on both the first device and the second device. The operation module 640 is used to allow the second device to perform an operation corresponding to the trusted authority on the first device. The information determination module 650 is used to determine the association relationship between the user and the device, and the user's operating authority for the device based on the association indication sent by the client. The association information generation module 660 is used to generate the association information of the device, wherein the association information includes the user identification of the associated user of the device, and the associated user's operating authority for the device. The association information sending module 670 is used to send the association information to the device, wherein different devices are allowed to perform operations corresponding to the trusted authority when it is determined based on the association information that there is a trusted authority, and the trusted authority is the operating authority that the associated user of different devices has for different devices.

[0069] In some embodiments, the first association information acquisition module 610 acquires the first association relationship corresponding to itself, including: acquiring a first trusted code from the cloud platform, the first trusted code is generated by the cloud platform based on the first association information of the first device, and decrypting the first trusted code to obtain the first association information.

[0070] In some embodiments, the first trusted code is obtained by the cloud platform using the encryption factor of the first device to encrypt the first associated information. The first associated information acquisition module 610 is used to execute the first device to obtain the first associated information corresponding to itself, and also includes: obtaining the decryption factor corresponding to the encryption factor sent by the cloud platform. The first associated information acquisition module 610 is specifically used to decrypt the first trusted code to obtain the first associated information, including: using the decryption factor to decrypt the first trusted code to obtain the first associated information.

[0071] In some embodiments, the first association information acquisition module 610 acquires the first trusted code from the cloud platform, including: in response to the first device currently satisfying any synchronization condition, sending a trusted code synchronization request to the cloud platform, wherein the synchronization condition includes at least one of the following: receiving an association change notification sent by the cloud platform, switching from an offline state to an online state, receiving an access control request from a second device and the first trusted code does not exist locally, receiving an access control request from a second device and the local first trusted code has expired, the association change notification is sent by the cloud platform at the request of the associated user of the first device, or the associated user of the first device to change the operation authority of the first device, and the validity period of the first trusted code is determined based on the valid timestamp when the first association information contains a valid timestamp. Receive the first trusted code sent by the cloud platform in response to the trusted code synchronization request.

[0072] In some embodiments, the first association information acquisition module 610 further includes a first association relationship clearing module, which is used to determine the disassociation between the first device and its associated user based on the association change notification sent by the cloud platform, and clear the first association information stored locally.

[0073] In some embodiments, the first association information acquisition module 610 further includes a first association relationship clearing module, and the first association relationship clearing module is used to determine that the first trusted code has expired and clear the first association relationship stored locally.

[0074] In some embodiments, the second association information acquisition module 620 is specifically used to obtain the second association relationship corresponding to the second device, including: receiving the second association information sent by the second device; or, receiving the second trusted code sent by the second device, wherein the second trusted code is generated by the cloud platform based on the second association information; decrypting the second trusted code to obtain the second association information.

[0075] In some embodiments, the type of associated users includes at least one of a shared user and a bound user, and the bound user has all operation permissions.

[0076] In some embodiments, the trusted authority acquisition module 630 is specifically used to determine the trusted authority between the first device and the second device based on the first association information and the second association information, including: comparing the first user identifier and the second user identifier to determine whether the first device and the second device have a common associated user; in response to the existence of a common associated user, obtaining the first operation permission of the common associated user for the first device, and the second operation permission of the common associated user for the second device; obtaining the intersection of the first operation permission and the second operation permission as the trusted authority.

[0077] In some embodiments, the associated information sending module 670 is specifically used to encrypt the associated information using the encryption factor of the device to obtain the trusted code of the device, and send the trusted code and the decryption factor corresponding to the encryption factor to the device.

[0078] In some embodiments, before the associated information sending module 670 encrypts the associated information using the encryption factor of the device to obtain the trusted code of the device, it also includes: generating an encryption factor of the device using the device identification of the device and a random character of a specific number of bits.

[0079] In some embodiments, the association indication is an indication of establishing an association relationship or an indication of changing an association relationship. The device management device 600 also includes a trusted code clearing module and a user device status sending module. Before the information determination module 650 is used to determine the association relationship between the user and the device and the user's operating authority for the device based on the association indication sent by the client, it also includes: before determining the association relationship between the user and the device and the user's operating authority for the device based on the association indication sent by the client, it also includes: receiving a relationship change indication sent by the client. In response to the relationship change indication being the association release indication, clearing the trusted code of the device stored locally. In response to the relationship change indication being the association change indication, executing the association indication sent by the client to determine the association relationship between the user and the device and the user's operating authority for the device. Sending an association change notification to the device. Among them, the trusted code clearing module is used to clear the trusted code of the device stored locally in response to the relationship change indication being the association release indication. The user device status sending module is used to send an association change notification to the device.

[0080] In some embodiments, the type of associated users includes at least one of a shared user and a bound user, and the bound user has all operation permissions.

[0081] In some embodiments, the association information further includes a validity period timestamp of the association information.

[0082] See also Figure 7 , Figure 7 : is a schematic diagram of a framework of an embodiment of an electronic device of the present application. The electronic device 70 includes a memory 71 and a processor 72 coupled to each other, and the processor 72 is used to execute program instructions stored in the memory 71 to implement the steps in any of the above-mentioned device management method embodiments. In a specific implementation scenario, the electronic device 70 may include but is not limited to: a microcomputer, a server, and in addition, the electronic device 70 may also include a mobile device such as a laptop computer and a tablet computer, which is not limited here.

[0083] Specifically, the processor 72 is used to control itself and the memory 71 to implement the steps in any of the above-mentioned device management method embodiments. The processor 72 can also be called a CPU (Central Processing Unit). The processor 72 may be an integrated circuit chip with signal processing capabilities. The processor 72 can also be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field-programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. In addition, the processor 72 can be implemented by an integrated circuit chip.

[0084] See also Figure 8 , Figure 8 The computer-readable storage medium 80 stores program instructions 81 that can be executed by a processor, and the program instructions 81 are used to implement the steps in any of the above device management method embodiments.

[0085] In some embodiments, the functions or modules included in the device provided by the embodiments of the present disclosure can be used to execute the method described in the above method embodiments. The specific implementation can refer to the description of the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0086] The above description of various embodiments tends to emphasize the differences between the various embodiments. The same or similar aspects can be referenced to each other, and for the sake of brevity, they will not be repeated herein.

[0087] In the several embodiments provided in the present application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device implementation described above is only schematic. For example, the division of modules or units is only a logical function division. There may be other division methods in actual implementation, such as units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

[0088] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0089] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of each implementation method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code.

Claims

1. A device management method, characterized in that: The method comprises: The first device acquires first association information corresponding to itself, wherein the first association information includes a first user identifier of an associated user of the first device and an operation authority of the associated user of the first device on the first device; Acquire second association information corresponding to the second device, wherein the second association information includes a second user identifier of an associated user of the second device and operation authority of the associated user of the second device on the second device; Determine, based on the first association information and the second association information, a trusted authority between the first device and the second device, wherein the trusted authority is an operation authority that a common associated user of the first device and the second device has on both the first device and the second device; The second device is allowed to perform an operation corresponding to the trusted authority on the first device.

2. The method according to claim 1, characterized in that The first device obtains first associated information corresponding to itself, including: Acquire a first trusted code from a cloud platform, where the first trusted code is generated by the cloud platform based on first associated information of the first device; The first trusted code is decrypted to obtain the first associated information.

3. The method according to claim 2, characterized in that The first trusted code is obtained by the cloud platform encrypting the first associated information using an encryption factor of the first device; The first device acquires the first association information corresponding to itself, further comprising: Obtaining a decryption factor corresponding to the encryption factor sent by the cloud platform; The decrypting the first trusted code to obtain the first associated information includes: The first trusted code is decrypted using the decryption factor to obtain the first associated information.

4. The method according to claim 2, characterized in that: The obtaining of the first trusted code from the cloud platform includes: In response to the first device currently satisfying any synchronization condition, sending a trusted code synchronization request to the cloud platform, wherein the synchronization condition includes at least one of the following: receiving an association change notification sent by the cloud platform, switching from an offline state to an online state, receiving an access control request from the second device and the first trusted code does not exist locally, receiving an access control request from the second device and the local first trusted code has expired, the association change notification is sent by the cloud platform at the request of an associated user of the first device, or an associated user of the first device to change the operation authority of the first device, and the validity period of the first trusted code is determined based on the validity timestamp when the first association information includes a validity timestamp; Receiving the first trusted code sent by the cloud platform in response to the trusted code synchronization request; And / or, the method further comprises at least one of the following steps: Based on the association change notification sent by the cloud platform, determine that the first device is disassociated from its associated user, and clear the first association information stored locally; It is determined that the first credible code has expired, and the first associated information stored locally is cleared.

5. The method according to claim 1, characterized in that The acquiring the second association information corresponding to the second device includes: receiving the second association information sent by the second device; or, Receive a second trusted code sent by the second device, wherein the second trusted code is generated by the cloud platform based on the second associated information; decrypt the second trusted code to obtain the second associated information.

6. The method according to claim 1, characterized in that The type of the associated user includes at least one of a sharing user and a bound user, and the bound user has all operation permissions; And / or, determining the trusted authority between the first device and the second device based on the first association information and the second association information includes: Comparing the first user identifier and the second user identifier to determine whether the first device and the second device have a common associated user; In response to the existence of the common associated user, obtaining a first operation permission of the common associated user on the first device and a second operation permission of the common associated user on the second device; An intersection of the first operation permission and the second operation permission is obtained as the trusted permission.

7. A device management method, characterized in that: include: Determine, based on the association indication sent by the client, an association relationship between the user and the device, and the user's operation authority for the device; Generate association information of the device, wherein the association information includes a user identifier of an associated user of the device and the associated user's operation authority for the device; The association information is sent to the device, wherein different devices allow each other to perform operations corresponding to the trusted authority when it is determined that there is a trusted authority based on the association information, and the trusted authority is the operation authority that a common associated user of the different devices has for different devices.

8. The method according to claim 7, characterized in that The sending the association information to the device includes: Encrypting the associated information using an encryption factor of the device to obtain a trusted code of the device; A trusted code and a decryption factor corresponding to the encryption factor are sent to the device.

9. The method according to claim 8, characterized in that Before encrypting the associated information using the encryption factor of the device to obtain the trusted code of the device, the method further includes: An encryption factor of the device is generated using the device identification of the device and a random character of a specific number of digits.

10. The method according to claim 7, characterized in that The association instruction is an association relationship establishment instruction or an association relationship change instruction; Before determining the association relationship between the user and the device and the user's operation authority over the device based on the association indication sent by the client, the method further includes: receiving a relationship change indication sent by the client; In response to the relationship change indication being the association release indication, clearing the locally stored trusted code of the device; In response to the relationship change indication being the association relationship establishment indication or the association relationship change indication, executing the association indication sent based on the client, determining the association relationship between the user and the device, and the user's operation authority for the device; An association change notification is sent to the device.

11. The method according to claim 7, characterized in that The type of the associated user includes at least one of a sharing user and a bound user, and the bound user has all operation permissions; And / or, the association information also includes a validity period timestamp of the association information.

12. An electronic device, characterized in that: The electronic device includes a memory and a processor, the memory stores program instructions, and the processor is used to execute the program instructions to implement the device trusted relationship establishment method as described in any one of claims 1-11.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store program instructions, and the program instructions can be executed to implement the device trusted relationship establishment method as described in any one of claims 1-11.

Images