CN108737440B - Method, server and computer readable storage medium for equipment management - Google Patents

Method, server and computer readable storage medium for equipment management Download PDF

Info

Publication number
CN108737440B
CN108737440B CN201810567337.9A CN201810567337A CN108737440B CN 108737440 B CN108737440 B CN 108737440B CN 201810567337 A CN201810567337 A CN 201810567337A CN 108737440 B CN108737440 B CN 108737440B
Authority
CN
China
Prior art keywords
account
request
authority
shared
equipment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810567337.9A
Other languages
Chinese (zh)
Other versions
CN108737440A (en
Inventor
姚德成
王凯
于晓光
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Axalent Solutions Shanghai Co ltd
Original Assignee
Axalent Solutions Shanghai Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Axalent Solutions Shanghai Co ltd filed Critical Axalent Solutions Shanghai Co ltd
Priority to CN201810567337.9A priority Critical patent/CN108737440B/en
Publication of CN108737440A publication Critical patent/CN108737440A/en
Application granted granted Critical
Publication of CN108737440B publication Critical patent/CN108737440B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/20Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102Entity profiles
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/20Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • H04L63/205Network architectures or network communication protocols for network security for managing network security; network security policies in general involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Power Engineering (AREA)
  • Telephonic Communication Services (AREA)
  • Selective Calling Equipment (AREA)

Abstract

The embodiment of the invention relates to the field of Internet of things, and discloses a device management method, a server and a computer-readable storage medium. The equipment management method of the invention comprises the following steps: receiving a device authority sharing request of a request account; acquiring the control authority of a request account to each device to be shared according to the device authority sharing request; judging whether the control authority of the request account on each device to be shared comprises a sharing authority or not, and determining a target account according to a judgment result; and aiming at each target account, distributing the identifier of the equipment to be shared in the mapping relation and the control authority of the equipment to be shared set by the target account to the corresponding target account according to the equipment authority sharing request, and managing the corresponding equipment to be shared by the target account according to the control authority of the equipment to be shared set by the target account. The equipment management method of the invention can meet the management requirements of different users on the intelligent equipment under different situations, and improve the safety and flexibility of the intelligent equipment management.

Description

Method, server and computer readable storage medium for equipment management
Technical Field
The embodiment of the invention relates to the field of Internet of things, in particular to a device management method, a server and a computer-readable storage medium.
Background
The intelligent home connects various intelligent devices (such as audio and video devices, lighting systems, curtain control, air conditioner control, security systems, digital cinema systems, audio and video servers, video cabinet systems, network home appliances and the like) in the home through the Internet of things technology, and provides multiple functions and means such as home appliance control, lighting control, telephone remote control, indoor and outdoor remote control, anti-theft alarm, environment monitoring, heating and ventilation control, infrared forwarding, programmable timing control and the like.
For better management of various intelligent devices, a user can control the various intelligent devices through the intelligent home platform, usually, a plurality of intelligent devices are bound under an account of an owner of the intelligent devices, and the owner of the intelligent devices manages the intelligent devices under the account of the owner of the intelligent devices by logging in the intelligent home platform.
The inventor finds that at least the following problems exist in the prior art: because the situation that a plurality of people need to use the intelligent equipment exists, the current intelligent equipment allows a plurality of users to be bound, different users can only log in a platform at different times to realize the management of the equipment, and the equipment management mode can not meet the requirement that the plurality of people manage the equipment simultaneously; the bound multiple users have the same control authority on the intelligent equipment, so that the safety problem exists; and the account number allowed to be bound by each intelligent device is limited, and when the user needing to use the intelligent device exceeds the situation of the number of the accounts allowed to be bound by the intelligent device, the requirement of people for managing the intelligent device cannot be met, so that the management flexibility of the intelligent device is poor.
Disclosure of Invention
The embodiment of the invention aims to provide a device management method, a server and a computer readable storage medium, so that the management requirements of different users on intelligent devices are met under different situations, and the safety and the flexibility of intelligent device management are improved.
In order to solve the above technical problem, an embodiment of the present invention provides a method for device management, which is applied to a device management platform, and includes: receiving an equipment authority sharing request of a request account, wherein the equipment authority sharing request comprises at least one mapping relation, and each mapping relation is mapping among an identifier of equipment to be shared, a pre-sharing account and a control authority of the equipment to be shared, which is set for the pre-sharing account; acquiring the control authority of a request account to each device to be shared according to the device authority sharing request; judging whether the control authority of each device to be shared of the request account includes a sharing authority, and determining a target account according to a judgment result, wherein the target account is as follows: the judgment result is a pre-sharing account in the mapping relation of the device to be shared including the sharing authority; and aiming at each target account, distributing the identifier of the equipment to be shared in the mapping relation and the control authority of the equipment to be shared set by the target account to the corresponding target account according to the equipment authority sharing request, and managing the corresponding equipment to be shared by the target account according to the control authority of the equipment to be shared set by the target account.
An embodiment of the present invention further provides a server, including: at least one processor; and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method for device management.
Embodiments of the present invention also provide a computer-readable storage medium storing a computer program, which when executed by a processor implements the above-mentioned method for device management.
Compared with the prior art, the method and the device have the advantages that the control authority of the request account for the bound device can be shared to a plurality of target accounts at the same time through a plurality of mapping relations, and the requirement of a plurality of people on the management of the same device is met. Because the device authority sharing request of the request account carries at least one mapping relation, the step of distributing the control authority of the device to be shared is simplified, and the request account can rapidly realize the management of a plurality of people on the same device; each mapping relation comprises an identifier of a device to be shared, a pre-sharing account and a control authority of the device to be shared, which is set for the pre-sharing account, so that the control authority of each target account to the device to be shared is different, and the control authority of each account is different, so that the probability of conflict when different accounts manage the same device is greatly reduced, the requirement of simultaneously managing the same device by multiple persons can be met, the number of the target accounts is not limited, and the flexibility of device management is improved; the control authority of the request account on each device to be shared is detected, the mapping relation without the sharing function is checked, the sharing step is simplified, and meanwhile the management safety of the devices to be shared can be guaranteed.
In addition, for each target account, according to the device permission sharing request, the device identifier to be shared in the mapping relationship and the control permission of the device to be shared set by the target account are allocated to the corresponding target account, which specifically includes: acquiring the identifier of the device to be shared in the mapping relation and the control authority to be shared set by the target account; adding a device identifier to be shared and a control authority of the device to be shared set by the target account in the target account; wherein, waiting to share equipment includes: virtual devices and/or physical devices. In the embodiment, the sharing of the control authority of the device to be shared can be realized only by adding the identifier of the device to be shared and the control authority of the device to be shared of the target account device in the target account, so that the allocation step is simple and the speed is high; meanwhile, various types of devices to be shared are provided, and both entity devices and virtual devices can manage the sub-devices, so that the flexibility of the devices to be shared is enhanced, and the applicability and the flexibility of the device management method are improved.
In addition, before receiving a device permission sharing request requesting an account, the device management method further includes: receiving a friend query request of a request account, wherein the friend query request is used for requesting to acquire friend list information of the request account, and the friend list is used for storing friend account information; if the pre-sharing account does not exist in the friend list of the request account, receiving a friend adding request and sending the friend adding request to the pre-sharing account; and adding the pre-sharing account into the friend list of the request account according to a response result returned by the pre-sharing account. In the embodiment, whether the pre-sharing account is a friend of the request account can be determined by inquiring the friend list in the request account, and the control authority of the device is shared only after the pre-sharing account is determined to exist in the friend list of the request account.
In addition, if there is a device to be shared that manages the child device, before adding the device identifier to be shared and the control authority of the device to be shared set by the target account to the target account, the device management method further includes: acquiring a device identifier to be shared of the management sub-device in a mapping relation of a target account; acquiring an identifier of each managed entity sub-device and/or an identifier of each managed virtual sub-device according to the acquired identifier of the device to be shared of the management sub-device; and updating the control authority corresponding to each managed entity sub-device identifier and/or virtual sub-device identifier into the control authority of the target account for the identifier of the device to be shared. In this embodiment, if there is a device to be shared that manages the sub-device, the managed sub-device may be a virtual device or an entity device, and the device to be shared that shares one managed sub-device can share the managed multiple entity sub-devices and/or virtual sub-devices, which further simplifies the step of sharing the control permissions of multiple devices simultaneously.
In addition, the equipment authority sharing request also comprises authentication information of a request account; according to the device permission sharing request, acquiring the control permission of the request account on each device to be shared, specifically comprising: acquiring identity authentication information of a request account; determining the identification of the request account according to the identity authentication information of the request account; and aiming at each device to be shared in the device permission sharing request, determining the control permission of the device to be shared by the request account according to the identifier of the device to be shared and the identifier of the request account. In the embodiment, the identification of the request account is determined by obtaining the authentication information of the request account, the security of the device permission sharing request can be ensured because the authentication information corresponds to the identification of the request account, and meanwhile, the control permission of the request account on the device to be shared can be quickly determined because the identification of the request account corresponds to the identification of the device to be shared one by one.
In addition, the sharing authority is set for the request account by the device management platform when the device to be shared is added to the request account for the first time, or the sharing authority is set for the request account by the device management platform according to the device authority sharing request received by the request account when the request account is used as the target account. In the embodiment, the sharing authority is set through the device management platform, so that the security of the sharing authority can be ensured, and the sharing authority in the request account can be set when the device to be shared is added for the first time or can be set according to device authority sharing requests sent by other accounts when the request account is used as a target account; through two ways of setting sharing permission, the flexibility of setting the sharing permission is improved.
In addition, the control authority includes: a first right, a second right, a third right, a fourth right, a fifth right and a sixth right; the first right includes: the method comprises the steps of sharing permission, canceling permission, checking equipment state information permission, first control equipment permission and first deleting equipment permission, wherein the sharing permission is to delete current equipment from a specified account containing current equipment identification, the first deleting equipment permission is to delete the current equipment from all accounts containing the current equipment identification, and the first control equipment permission is to control all functions of the equipment; the second right includes: viewing the device state information authority, the first control device authority and a second deleting device authority, wherein the second deleting authority is the current device deleted from the current account; the third right includes: checking the device state information authority and the first control device authority; the fourth right includes: checking the device state information authority; the fifth right includes: checking the device state information authority and a second control device authority, wherein the second control device authority is a partial function authority of the control device; the sixth right includes: and viewing the partial state information authority of the equipment. Different kinds of control authorities are provided in the embodiment, so that the requirement of different users on management of the same equipment can be met.
In addition, according to the device permission sharing request, after the control permission of the device to be shared, which is set for the target account in the mapping relationship, is allocated to the corresponding target account, the method further includes: receiving a management equipment request of a target account, wherein the management equipment request comprises an identifier of equipment to be managed and operation information of the equipment to be managed; and detecting whether the control authority of the target account to-be-managed equipment identification meets a preset condition or not according to the management equipment request, if so, managing the to-be-managed equipment by the target account, and otherwise, finishing the management. In this embodiment, the target account detects the control authority of the target account before the device to be managed is managed, so as to further ensure the security of device management.
Drawings
One or more embodiments are illustrated by way of example in the accompanying drawings, which correspond to the figures in which like reference numerals refer to similar elements and which are not to scale unless otherwise specified.
Fig. 1 is a flowchart illustrating a method for device management according to a first embodiment of the present invention;
fig. 2 is a flowchart of method steps included when a device to be shared includes a virtual device in a device management method according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of an apparatus for device management according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of a server according to a fourth embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, it will be appreciated by those of ordinary skill in the art that numerous technical details are set forth in order to provide a better understanding of the present application in various embodiments of the present invention. However, the technical solution claimed in the present application can be implemented without these technical details and various changes and modifications based on the following embodiments.
The first embodiment of the invention relates to a device management method, which is applied to a device management platform, such as an intelligent home management platform. The user can manage the equipment under the self account by logging in the corresponding account of the equipment management platform. A specific flow of the device management method in this embodiment is shown in fig. 1, and includes:
step 101: receiving an equipment authority sharing request of a request account, wherein the equipment authority sharing request comprises at least one mapping relation, and each mapping relation is mapping among an identifier of equipment to be shared, a pre-sharing account and a control authority of the equipment to be shared, which is set for the pre-sharing account.
Specifically, the device permission sharing request may include one mapping relationship, two mapping relationships, or more than two mapping relationships. If two or more mapping relationships are included, they may exist in the form of a mapping table. Each mapping relation is a mapping relation among the identifier of the device to be shared, the pre-sharing account and the control authority of the device to be shared, which is set for the pre-sharing account. The device to be shared is a unique and identifiable identifier of the device, and the device management platform can uniquely determine the device to be shared through the device to be shared. Certainly, the device permission sharing request may also carry other parameters, such as an identifier and an address of the request account; this embodiment is not limited to this, and may be set according to actual requirements.
It should be noted that, before receiving a device permission sharing request requesting an account, the method for device management further includes: receiving a friend query request of a request account, wherein the friend query request is used for requesting to acquire friend list information of the request account, and the friend list is used for storing friend account information; if the pre-sharing account does not exist in the friend list of the request account, receiving a friend adding request and sending the friend adding request to the pre-sharing account; and adding the pre-sharing account into the friend list of the request account according to a response result returned by the pre-sharing account.
Specifically, the device management platform manages accounts of different users, a request account initiates a friend query request to the device management platform, the device management platform receives the friend query request of the request account, the device management platform obtains friend list friend information of the request account according to the friend query request, a user corresponding to the request account judges whether a pre-sharing account exists in a current friend list or not according to the friend list information, if yes, the request account sends a device permission sharing request, and the device management platform directly executes step 101. If the friend list does not exist, the request account sends a friend adding request to the pre-sharing account through the equipment management platform, if a response result returned by the pre-sharing account is that the friend is added, the equipment management platform adds the pre-sharing account to the friend list of the request account, and then step 101 is executed; and if the response result returned by the pre-sharing account is that the addition of the friend is refused, ending the flow of the equipment management method. And the friend list information comprises account information of all added friends.
And sharing the control authority of the equipment after determining that the pre-sharing account exists in the friend list in the request account, wherein the pre-sharing account is a friend and is not other strangers, so that the safety of the control authority of the equipment to be shared is further ensured.
Step 102: and acquiring the control authority of the request account on each device to be shared according to the device authority sharing request.
In a specific implementation, if the device permission sharing request further includes authentication information of the request account, acquiring the authentication information of the request account; determining the identification of the request account according to the identity authentication information of the request account; and aiming at each device to be shared in the device permission sharing request, determining the control permission of the device to be shared by the request account according to the identifier of the device to be shared and the identifier of the request account.
Specifically, the identity authentication information of the request account may be a token (token), the device management platform obtains the token in the device permission sharing request, verifies the token, if the verification is passed, the request account is legal, if the verification fails, the request account is determined to be illegal, subsequent operations are not performed, and meanwhile, prompt information of the verification failure may be returned. Through the verification of the token, the control authority of the equipment can be prevented from being shared by lawless persons, and the safety of the equipment authority management is ensured.
It can be understood that the authentication information of each requesting account corresponds to the requesting account one by one, and thus after the authentication information of the requesting account is verified, the identifier of the current requesting account can be determined through the corresponding relationship between the authentication information and the requesting account. The device management platform can determine the control authority of the request account for each device to be shared according to the identifier of the request account and the identifier of each device to be shared, and the following description is given by taking an example of obtaining the control authority of the request account for one device to be shared.
For example, assume that the authentication information of the request account a corresponds to the identifier a of the request account, the request account a binds to the device a to be shared, and corresponds to the control authority AAA of the device a to be shared. If the identity authentication information of the request account passes the authentication, according to the corresponding relationship between the identity authentication information and the identification of the request account, the identification of the current request account can be determined to be A, and the storage position of the request account A can be quickly found, so that the device to be shared bound by the account A can be quickly obtained, and at the moment, the control authority of the request account A on the device to be shared is uniquely determined to be AAA by combining the identification a of the device to be shared.
Step 103: judging whether the control authority of each device to be shared of the request account includes a sharing authority, and determining a target account according to a judgment result, wherein the target account is as follows: and judging that the pre-sharing account number in the mapping relation of the device to be shared including the sharing authority is the pre-sharing account number.
Specifically, in order to ensure the security of sharing the device control authority, it is necessary to determine whether the control authority of the requesting account for each device to be shared includes a sharing authority. A specific example will be described below in detail of a process of determining the control authority of the device to be shared and determining the target account according to the determination result.
For example, assume that the request account a is to treat a control authority AA of the device 1 to be shared and a control authority BB of the device 2 to be shared, where the control authority AA includes a sharing authority and the control authority BB does not include the sharing authority. If the device management platform obtains the mapping relationship corresponding to the two devices to be shared in the device permission sharing request of the request account A, it can be determined that there are two devices to be shared, namely a device to be shared 1 and a device to be shared 2; and judging that the control authority of the device to be shared 1 includes the sharing authority, and determining that the pre-shared account in the mapping relation of the device to be shared 1 is the target account. And if the control authority of the device to be shared 2 does not include the sharing authority, determining that the pre-sharing account in the mapping relationship of the device to be shared 2 is not the target account.
It can be understood that the sharing authority is set for the request account by the device management platform when the device to be shared is added to the request account for the first time; or the sharing authority is set for the request account by the device management platform according to the device authority sharing request received when the request account is used as the target account, for example, assuming that the control authority of the account B for the device 1 includes the sharing authority, the device management platform receives the device authority sharing request a sent by the account B, and at this time, the account a is used as the target account, and then the device management platform sets the sharing authority for the account a according to the received device authority sharing request a.
Step 104: and aiming at each target account, distributing the identifier of the equipment to be shared in the mapping relation and the control authority of the equipment to be shared set by the target account to the corresponding target account according to the equipment authority sharing request, and managing the corresponding equipment to be shared by the target account according to the control authority of the equipment to be shared set by the target account.
In one specific implementation, the device management platform acquires the identifier of the device to be shared in the mapping relation and the control authority to be shared set by the target account; and adding the identifier of the device to be shared and the control authority of the device to be shared set by the target account in the target account.
Specifically, each account (request account and target account) may manage different devices through a device identifier list, and the target account may add a device identifier and a control authority of a device to be shared, which is set for the target account.
It can be understood that a device to be shared is added to a management device list in a target account, and a corresponding control authority is set for the device to be shared. In the embodiment, in order to adapt to different use situations, six control authorities are determined, namely a first authority, a second authority, a third authority, a fourth authority, a fifth authority and a sixth authority; the first right includes: the method comprises the steps of sharing permission, canceling the sharing permission, checking the permission of equipment state information, the permission of a first control device and the permission of a first deleting device, wherein the canceling of the sharing permission is to delete the current equipment from a specified account containing a current equipment identifier, the permission of the first deleting device is to delete the current equipment from all accounts containing the current equipment identifier, and the permission of the first control device is to control all functions of the equipment; the second right includes: viewing the device state information authority, the first control device authority and a second deleting device authority, wherein the second deleting authority is the current device deleted from the current account; the third right includes: checking the device state information authority and the first control device authority; the fourth right includes: checking the device state information authority; the fifth right includes: checking the device state information authority and a second control device authority, wherein the second control device authority is a partial function authority of the control device; the sixth right includes: and viewing the partial state information authority of the equipment.
It should be noted that the first right is the highest-level right, and at the same time, only the first right includes the sharing right, and the sharing right is cancelled. Similarly, only one account has the first control right for the same device. The functions included in the respective rights will be described below as a specific example.
For example, if the control authority of the target account a on the device 1 is the second authority, the target account a may view the state information of the device 1, control all functions of the device 1 (e.g., controlling the device 1 to turn on or off), and may delete the device 1 from the target account a. If the control authority of the target account B on the device 2 is the fifth authority, the target account B may view all the state information of the device 2, control a part of the functions of the device 2, and assume that the device 2 has 3 functions (function 1, function 2, and function 3), and the target account B may control the function 1 of the device 2. Assuming that the control authority of the request account C on the device 3 is the first authority, the request account C may share the control authority set on the device 3 to the target account 4, view all state information of the device 3, control all functions of the device 3, delete the device 3 from the request account C, and delete the device 3 from the target account 4, and of course, the request account C may also delete the device identifier of the device 3 from the target account 4, thereby achieving the purpose of cancelling the sharing.
Step 105: and receiving a management equipment request of the target account, wherein the management equipment request comprises an identifier of equipment to be managed and operation information of the equipment to be managed.
Specifically, the management device request of the target account may be sent when a management operation is triggered, where the operation information on the management device may be specific operation content. For example, assuming that the device to be managed is an intelligent air conditioner, the temperature adjustment button is triggered by the device management platform, and then a temperature adjustment request can be sent, where the request may include an identifier of the device to be managed and temperature adjustment control information.
Step 106: and detecting whether the control authority of the target account to the device identifier to be managed meets a preset condition or not according to the management device request, if so, executing the step 107, and otherwise, ending the management.
Specifically, the management device request also carries the identifier of the target account, and the control authority of the device to be managed can be determined through the identifier of the target account and the identifier of the device to be managed. The preset condition may be set according to an actual situation, for example, the control authority corresponding to each operation information is used as the preset condition. And judging whether the current authority of the equipment to be managed meets the control authority corresponding to the operation information. For example, if the control authority corresponding to the temperature adjustment operation information is "first control device authority", it is determined whether the control authority of the current device to be managed includes the first control device authority, if so, it is determined that the preset condition is satisfied, otherwise, it is determined that the preset condition is not satisfied.
Step 107: and the target account manages the equipment to be managed.
Before each time of managing the equipment, the control authority of the target account on the equipment to be managed is detected, and the safety of managing the equipment is further ensured.
Compared with the prior art, the method and the device have the advantages that the control authority of the request account for the bound device can be shared to a plurality of target accounts at the same time through a plurality of mapping relations, and the requirement of a plurality of people on the management of the same device is met. Because the device authority sharing request of the request account carries at least one mapping relation, the step of distributing the control authority of the device to be shared is simplified, and the request account can rapidly realize the management of a plurality of people on the same device; each mapping relation comprises an identifier of a device to be shared, a pre-sharing account and a control authority of the device to be shared, which is set for the pre-sharing account, so that the control authority of each target account to the device to be shared is different, and the control authority of each account is different, so that the probability of conflict when different accounts manage the same device is greatly reduced, the requirement of simultaneously managing the same device by multiple persons can be met, the number of the target accounts is not limited, and the flexibility of device management is improved; the control authority of the request account on each device to be shared is detected, the mapping relation without the sharing function is checked, the sharing step is simplified, and meanwhile the management safety of the devices to be shared can be guaranteed.
A second embodiment of the present invention relates to a method of device management. The second embodiment is an improvement of the first embodiment, and the main improvements are as follows: in a second embodiment of the present invention, a device to be shared includes: virtual devices and/or physical devices; if there is a device to be shared that manages a child device, the device management method further includes the steps shown in fig. 2 before adding the device identifier to be shared and the control authority of the device to be shared set by the target account to the target account.
It can be understood that the devices to be shared may include virtual devices and physical devices; or the device to be shared comprises a virtual device; or the device to be shared comprises an entity device. The physical device may be an electric light, a washing machine, a television, or the like having a physical body. The virtual device may be a cloud, various management platforms, and the like, and the virtual device may be used to manage other physical devices or virtual devices, for example, the virtual device may be a management platform that manages an entire floor light, a management platform that manages all intelligent devices in one room, a platform that manages plant devices, or a platform that manages project engineering devices, and the like. If the device is a cloud, the device can be a cloud of different management devices. Of course, the virtual device may not manage other devices, but only be used for implementing specific functions, such as a virtual network card, a virtual driver, and the like. The specific type of the virtual device may not be limited to the type provided in this embodiment, and the specific type may be set according to actual needs.
Step 201: and acquiring the identifier of the device to be shared of the management sub-device in the mapping relation of the target account.
Specifically, the device management platform acquires a device identifier to be shared in a mapping relation of a target account, judges whether a sub-device is managed under the device identifier to be shared, acquires the device identifier to be shared of the managed sub-device if the sub-device is managed under the device identifier to be shared, and otherwise determines that the sub-device is not managed under the current device identifier to be shared. Of course, it may also be determined whether the current device to be shared manages the child device in other manners, for example, a specific tag may be added to the identifier of the device to be shared that manages the child device, and it may be determined whether the current device to be shared manages the child device by identifying the identifier of the device to be shared. In this embodiment, the identifiers of the virtual devices to be shared in the mapping relationship where the other acquired target account is located are not listed one by one.
Step 202: and acquiring each managed entity sub-device identifier and/or virtual sub-device identifier according to the acquired device identifier to be shared of the management sub-device.
Specifically, the sub-devices may be virtual devices or physical devices, and the virtual devices may implement their own specific functions, or manage the physical sub-devices, or manage the virtual sub-devices, or manage both the physical sub-devices and the virtual sub-devices. The entity equipment can realize the specific functions of the entity equipment, and can also manage other entity sub-equipment, such as an intelligent television, can realize the specific functions of the television, and can also manage an intelligent air conditioner, an intelligent electric lamp and the like. Of course, the managed sub-device may be one or more. The present embodiment does not limit the number of managed sub-devices
Step 203: and updating the control authority corresponding to each managed entity sub-device identifier and/or virtual sub-device identifier into the control authority of the target account for the identifier of the device to be shared.
Specifically, because the device to be shared manages at least one entity device and/or virtual device, if no other sub device exists under the managed sub device, the control authority of the entity sub device managed by the device to be shared is updated to the control authority of the current target account on the device to be shared. If other sub-devices exist under the managed sub-device, the step 202 is continuously repeated to obtain the sub-device identifier bound under the managed sub-device, and the step 203 is continuously repeated until the control permissions of all the sub-devices under the device to be shared are updated.
For example, if the device a to be shared in the mapping relationship where the target account 1 is located manages the virtual sub-device B and the entity sub-device C, the virtual sub-device B manages the entity sub-device D, the control right of the virtual device a to the virtual sub-device B is the second right, the control right of the virtual device a to the entity sub-device C is the third right, and the control right of the virtual sub-device B to the entity sub-device D is the fifth right. Assuming that the control authority of the target account 1 on the virtual device a to be shared is set as a fourth authority, device identifiers of the managed virtual sub-device B and the entity sub-device C are obtained, the control authority of the virtual device a on the virtual sub-device B is updated to the fourth authority, and the control authority of the virtual device a on the entity sub-device C is set as the fourth authority.
In the device management method provided in this embodiment, if there is a device to be shared that manages a sub device, the managed sub device may be a virtual device or an entity device, and a device to be shared that shares a management sub device can share the managed multiple entity sub devices and/or multiple virtual sub devices, which further simplifies the step of sharing the control permissions of multiple devices simultaneously.
A third embodiment of the present invention relates to an apparatus for device management 30, including: the specific structure of the receiving module 301, the obtaining module 302, the determining module 303 and the allocating module 304 is shown in fig. 3.
The receiving module 301 is configured to receive an equipment permission sharing request requesting an account, where the equipment permission sharing request includes at least one mapping relationship, and each mapping relationship is a mapping between an identifier of a device to be shared, a pre-sharing account, and a control permission of the device to be shared, which is set for the pre-sharing account.
The obtaining module 302 is configured to obtain, according to the device permission sharing request, a control permission of the request account for each device to be shared; the determining module 303 is configured to determine whether the control authority of the request account for each device to be shared includes a sharing authority, and determine a target account according to a determination result, where the target account is: the judgment result is a pre-sharing account in the mapping relation of the device to be shared including the sharing authority; for each target account, the allocating module 304 is configured to allocate, according to the device permission sharing request, the device identifier to be shared in the mapping relationship and the control permission of the device to be shared set by the target account to the corresponding target account, and manage, by the target account, the corresponding device to be shared according to the control permission of the device to be shared set by the target account.
It should be understood that this embodiment is a system example corresponding to the first embodiment, and may be implemented in cooperation with the first embodiment. The related technical details mentioned in the first embodiment are still valid in this embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related-art details mentioned in the present embodiment can also be applied to the first embodiment.
It should be noted that each module referred to in this embodiment is a logical module, and in practical applications, one logical unit may be one physical unit, may be a part of one physical unit, and may be implemented by a combination of multiple physical units. In addition, in order to highlight the innovative part of the present invention, elements that are not so closely related to solving the technical problems proposed by the present invention are not introduced in the present embodiment, but this does not indicate that other elements are not present in the present embodiment.
A fourth embodiment of the present invention relates to a server 40 including: at least one processor 401; and a memory 402 communicatively coupled to the at least one processor 401; the memory 402 stores instructions executable by the at least one processor 401, and the instructions are executed by the at least one processor 401, so that the at least one processor 401 can execute the above-mentioned device management method.
The memory 402 and the processor 401 are connected by a bus, which may include any number of interconnected buses and bridges that link one or more of the various circuits of the processor 401 and the memory 402. The bus may also link various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface provides an interface between the bus and the transceiver. The transceiver may be one element or a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor 401 may be transmitted over a wireless medium via an antenna, which may receive the data and transmit the data to the processor 401.
The processor 401 is responsible for managing the bus and general processing and may provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And the memory may be used to store data used by the processor in performing operations.
Those skilled in the art can understand that all or part of the steps in the method of the foregoing embodiments may be implemented by a program to instruct related hardware, where the program is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific examples for carrying out the invention, and that various changes in form and details may be made therein without departing from the spirit and scope of the invention in practice.

Claims (10)

1. A method for device management is applied to a device management platform, and comprises the following steps:
receiving an equipment authority sharing request of a request account, wherein the equipment authority sharing request comprises at least one mapping relation, and each mapping relation is mapping among an identifier of equipment to be shared, a pre-sharing account and a control authority set for the pre-sharing account on the equipment to be shared;
acquiring the control authority of the request account on each device to be shared according to the device authority sharing request;
judging whether the control authority of the request account on each device to be shared includes a sharing authority, and determining a target account according to a judgment result, wherein the target account is as follows: the judgment result is a pre-sharing account in the mapping relation of the device to be shared including the sharing authority;
and for each target account, distributing the identifier of the device to be shared in the mapping relation and the control authority of the device to be shared set by the target account to the corresponding target account according to the device authority sharing request, and managing the corresponding device to be shared by the target account according to the control authority of the device to be shared set by the target account.
2. The device management method according to claim 1, wherein for each target account, according to the device permission sharing request, allocating the device identifier to be shared and the control permission of the device to be shared, which is set by the target account, to the corresponding target account in the mapping relationship, specifically includes:
acquiring the identifier of the device to be shared in the mapping relation and the control authority to be shared set by the target account;
adding the identifier of the device to be shared and the control authority of the device to be shared set by the target account into the target account;
wherein, the equipment to share includes: virtual devices and/or physical devices.
3. The device management method according to claim 1, wherein before the receiving the device permission sharing request requesting the account, the device management method further includes:
receiving a friend query request of the request account, wherein the friend query request is used for requesting to acquire friend list information of the request account, and the friend list is used for storing friend account information;
if the pre-sharing account does not exist in the friend list of the request account, receiving a friend adding request and sending the friend adding request to the pre-sharing account;
and adding the pre-sharing account into the friend list of the request account according to a response result returned by the pre-sharing account.
4. The device management method according to claim 2, wherein if there is a device to be shared that manages a child device, before adding the device to be shared identifier and the control right of the device to be shared that is set by the target account to the target account, the device management method further includes:
acquiring a device identifier to be shared of the management sub-device in a mapping relation of the target account;
acquiring each managed entity sub-device identifier and/or virtual sub-device identifier according to the acquired identifier of the device to be shared of the management sub-device;
and updating the control authority corresponding to each managed entity sub-device identifier and/or virtual sub-device identifier to the control authority of the target account on the identifier of the device to be shared.
5. The device management method according to any one of claims 1 to 4, wherein the device permission sharing request further includes authentication information of the request account;
according to the device permission sharing request, acquiring the control permission of the request account on each device to be shared, which specifically includes:
acquiring the identity verification information of the request account;
determining the identification of the request account according to the identity authentication information of the request account;
and determining the control authority of the request account on each device to be shared in the device authority sharing request according to the identifier of the device to be shared and the identifier of the request account.
6. The device management method according to claim 5, wherein the sharing authority is set for a request account by the device management platform when the device to be shared is added to the request account for the first time, or,
and the sharing authority is set for the request account by the equipment management platform according to the equipment authority sharing request received when the request account is used as a target account.
7. The method of device management according to claim 6, wherein the control authority comprises: a first right, a second right, a third right, a fourth right, a fifth right and a sixth right;
the first right includes: the method comprises the steps of sharing permission, canceling the sharing permission, checking equipment state information permission, first control equipment permission and first deleting equipment permission, wherein the canceling of the sharing permission is to delete current equipment from a specified account containing a current equipment identifier, the first deleting equipment permission is to delete the current equipment from all accounts containing the current equipment identifier, and the first control equipment permission is to control all functions of the equipment;
the second right includes: viewing the device state information authority, the first control device authority and a second deleting device authority, wherein the second deleting device authority is the current device deleted from the current account;
the third right includes: checking the device state information authority and the first control device authority;
the fourth right includes: checking the device state information authority;
the fifth right includes: viewing the device state information authority and a second control device authority, wherein the second control device authority is a partial function authority of the control device;
the sixth right includes: and viewing the partial state information authority of the equipment.
8. The device management method according to claim 6 or 7, wherein after allocating, according to the device permission sharing request, the control permission of the device to be shared, set for the target account in the mapping relationship, to the corresponding target account, the method further includes:
receiving a management equipment request of a target account, wherein the management equipment request comprises an identification of equipment to be managed and operation information of the equipment to be managed;
and detecting whether the control authority of the target account on the identification of the equipment to be managed meets a preset condition or not according to the request of the management equipment, if so, managing the equipment to be managed by the target account, and otherwise, finishing the management.
9. A server, comprising:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of device management according to any one of claims 1 to 8.
10. A computer-readable storage medium, in which a computer program is stored, which, when being executed by a processor, carries out the method of device management according to any one of claims 1 to 8.
CN201810567337.9A 2018-06-05 2018-06-05 Method, server and computer readable storage medium for equipment management Active CN108737440B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810567337.9A CN108737440B (en) 2018-06-05 2018-06-05 Method, server and computer readable storage medium for equipment management

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810567337.9A CN108737440B (en) 2018-06-05 2018-06-05 Method, server and computer readable storage medium for equipment management

Publications (2)

Publication Number Publication Date
CN108737440A CN108737440A (en) 2018-11-02
CN108737440B true CN108737440B (en) 2020-08-28

Family

ID=63932250

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810567337.9A Active CN108737440B (en) 2018-06-05 2018-06-05 Method, server and computer readable storage medium for equipment management

Country Status (1)

Country Link
CN (1) CN108737440B (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110519151B (en) * 2019-07-12 2021-06-01 湖南新云网科技有限公司 Controllable friend adding method and device, terminal equipment and storage medium
CN110535738A (en) * 2019-09-27 2019-12-03 四川长虹电器股份有限公司 Intelligent housing permission sharing method
CN111143857B (en) * 2019-12-27 2022-04-22 达闼机器人有限公司 Data sharing method, robot controller and storage medium
CN112598315B (en) * 2020-12-29 2023-10-10 广州极飞科技股份有限公司 Shared information generation method and device, job demand platform and electronic equipment
CN113114465B (en) * 2021-03-19 2022-10-11 青岛海尔科技有限公司 Method and device for processing attribution authority, storage medium and electronic device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015035783A1 (en) * 2013-09-11 2015-03-19 Tencent Technology (Shenzhen) Company Limited Systems and methods for instant messaging
CN106487622A (en) * 2016-10-24 2017-03-08 北京小米移动软件有限公司 Equipment control sharing method and device
CN107872373A (en) * 2017-09-30 2018-04-03 珠海格力电器股份有限公司 Equipment control sharing method, device, storage medium and server
CN107995215A (en) * 2017-12-20 2018-05-04 青岛海信智慧家居系统股份有限公司 Control method, device and the cloud platform server of smart home device

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015035783A1 (en) * 2013-09-11 2015-03-19 Tencent Technology (Shenzhen) Company Limited Systems and methods for instant messaging
CN106487622A (en) * 2016-10-24 2017-03-08 北京小米移动软件有限公司 Equipment control sharing method and device
CN107872373A (en) * 2017-09-30 2018-04-03 珠海格力电器股份有限公司 Equipment control sharing method, device, storage medium and server
CN107995215A (en) * 2017-12-20 2018-05-04 青岛海信智慧家居系统股份有限公司 Control method, device and the cloud platform server of smart home device

Also Published As

Publication number Publication date
CN108737440A (en) 2018-11-02

Similar Documents

Publication Publication Date Title
CN108737440B (en) Method, server and computer readable storage medium for equipment management
US9906956B1 (en) Using power-line networks to facilitate network access
US9948510B2 (en) Method and apparatus for managing access information for registration of device in smart home service
CN106992989B (en) Sharing authorization method of smart home, server and readable storage medium
KR102213640B1 (en) Apparatus and method for exporting information related to a home device of a user device in a home network system
CN106899547B (en) Equipment operation method based on Internet of things and server
US9479504B2 (en) Method and apparatus for controlling access between home device and external server in home network system
CN107528733B (en) Management method of Internet of things and Internet of things system
CN109474632B (en) Method, apparatus, system, and medium for authenticating and managing rights of user
KR102472362B1 (en) Internet Of Things Device Control System and Method Based On Block Chain
US11096051B2 (en) Connection establishment method, device, and system
US9178871B2 (en) Authentication and authorization method and system
CN110602216A (en) Method and device for using single account by multiple terminals, cloud server and storage medium
CN108023883B (en) Equipment authorization management method and device
CN109714333B (en) Household appliance and management method and device of control authority of household appliance and readable storage medium
KR20160121775A (en) THIRD PARTY'S SECURITY AUTHENTICATION SYSTEM BETWEEN MOBILE DEVICE AND IoT DEVICES AND METHOD THEREOF
CN114553592B (en) Method, equipment and storage medium for equipment identity verification
CN111092797A (en) Equipment control authority distribution method, device and system
CN109543365B (en) Authorization method and device
US8107384B2 (en) Information communication system, transmitting apparatus, transmitting method, and computer program
CN111047740A (en) Digital key sharing method
CN105488875A (en) Access control verification method and device
CN107666505B (en) Method and device for controlling resource access
CN105721441B (en) Identity authentication method in virtualization environment
CN107241332B (en) Gateway authority processing method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant