Device management method, system, platform and computer-readable storage medium

Abstract

A device management method includes: receiving a group registration request sent by a device driver, adding the device driver to the requested group after verifying the legitimacy of the device driver and the group access rights, and setting it according to the requested group processing capacity. The present invention also provides a system, a platform and a computer-readable storage medium for implementing the device management method. The present invention can manage device drivers in groups so that devices associated with the device driver can be managed in groups together.

Description

Technical Field

[0001] The present invention relates to the field of Internet of Things, and in particular to a device management method, system, platform and computer-readable storage medium. Background Art

[0002] Although device drivers can provide interfaces for IoT devices and applications to interact, at the current stage, there is still a lack of unified control, access and interoperability between devices from different manufacturers. In addition, devices are not connected in series through the services they provide, and it is not considered that the operating status of one device may affect the operation of other devices. Summary of the invention

[0003] In view of this, an object of the present invention is to provide a device management method, system, platform and computer-readable storage medium, which can integrate different device drivers and their associated devices, and perform group management and communication.

[0004] An embodiment of the present invention provides a device management method, the method comprising: receiving a group registration request sent by a device driver, wherein the group registration request includes a group name, identity information and a verification key of the device driver, a group access permission verification key, and a group processing capability; judging the legitimacy of the device driver according to the identity information and the verification password of the device driver, and when the device driver is judged to be a legal device driver, querying a group list to judge whether the group name already exists; when it is judged that the group name already exists, judging whether the device driver has group access permission according to the group access permission verification key; and when it is judged that the device driver has group access permission, updating the group list according to the identity information and the group processing capability of the device driver.

[0005] An embodiment of the present invention also provides a device management system, which includes a management platform and at least one device driver, wherein: the management platform receives a group registration request sent from the device driver, wherein the group registration request includes a group name, identity information and verification key of the device driver, group access permission verification key and group processing capability; the management platform verifies the legitimacy of the device driver based on the identity information and verification key of the device driver; the management platform verifies the group access permission of the device driver based on the group name and the group access permission verification key; and the management platform feeds back the group registration request processing result to the device driver based on the verification result.

[0006] An embodiment of the present invention further provides a device management platform, the platform comprising a processor and a memory, the memory is used to store at least one instruction, and the processor is used to execute the at least one instruction to implement the device management method.

[0007] An embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores at least one instruction, and when the at least one instruction is executed by a processor, the device management method is implemented.

[0008] Compared with the prior art, the device management method, apparatus, and computer-readable storage medium provided by the present invention can manage device drivers in groups, so as to manage devices associated with the device drivers in groups. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 FIG. 4 is a schematic diagram of the architecture of a device management system according to an embodiment of the present invention.

[0010] Figure 2 FIG. 4 is a schematic diagram of the relationship between a device and sub-devices according to an embodiment of the present invention.

[0011] Figure 3 FIG. 4 is a flow chart of a device management method according to an embodiment of the present invention.

[0012] Figure 4 FIG. 4 is a flow chart of a device management method according to another embodiment of the present invention.

[0013] Figure 5 FIG. 4 is a structural diagram of a management platform according to an embodiment of the present invention.

[0014] Main component symbols

[0015]

[0016]

[0017] The following specific implementation manner will further illustrate the present invention in conjunction with the above-mentioned drawings. DETAILED DESCRIPTION

[0018] In order to facilitate the understanding and implementation of the present invention by those skilled in the art of the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the present invention provides many applicable inventive concepts, which can be implemented in a variety of specific forms. Those skilled in the art of the present invention can use the details described in these embodiments or other embodiments and other available structural, logical and electrical changes to implement the invention without departing from the spirit and scope of the present invention.

[0019] The present invention specification provides different embodiments to illustrate the technical features of different implementations of the present invention. Among them, the configuration of each component in the embodiment is for illustration purposes and is not intended to limit the present invention. And the partial repetition of the figure numbers in the embodiment is to simplify the description and does not mean the correlation between different embodiments. Among them, the same component numbers used in the drawings and the description represent the same or similar components. The drawings in this specification are simplified and are not drawn to exact proportions.

[0020] Furthermore, in describing some embodiments of the present invention, the specification describes the method and (or) program of the present invention in a specific order of steps. However, since the method and program are not necessarily implemented according to the specific order of steps described, they are not limited to the specific order of steps described. A person skilled in the art of the present invention will know that other orders are also possible implementation methods. Therefore, the specific order of steps described in the specification is not used to limit the scope of the patent application. Furthermore, the scope of the patent application for the method and (or) program of the present invention is not limited to the order of execution steps written therein, and a person skilled in the art of the present invention will understand that adjusting the order of execution steps does not deviate from the spirit and scope of the present invention.

[0021] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those generally understood by those skilled in the art of the present invention. The terms used herein in the specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. The term "and / or" used herein includes any and all combinations of one or more related listed items. Some embodiments of the present invention are described in detail below in conjunction with the accompanying drawings.

[0022] See also Figure 1 , which is a schematic diagram of the architecture of a device management system according to an embodiment of the present invention. Figure 1 As shown, the system architecture includes: a management platform 100, multiple device drivers 110 and multiple devices 120. Among them, the multiple devices 120 can be various IoT devices in the IoT scenario, and the management platform 100 can be a management platform to which multiple devices 120 in the IoT scenario are connected. The multiple device drivers 120 serve as interfaces of the multiple devices 120, and provide device-independent service interfaces to applications in the IoT scenario. Applications only need to call interfaces corresponding to requirements according to specifications, without having to care about the actual device composition. In this embodiment, the management platform 100 is also used to manage the device drivers 110 of all devices 120.

[0023] In one embodiment, the management platform 100 may be a computer device such as a desktop, a mobile phone, a tablet computer, or a server. It should be noted that the management platform 100 is only an example, and other existing or future computer devices that can be adapted to the present invention should also be included in the protection scope of the present invention.

[0024] In some embodiments, the management platform 100 includes a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application-specific integrated circuits, programmable gate arrays, digital processors, and embedded devices.

[0025] It should be noted that Figure 1 The number of the multiple device drivers 110, the number of the multiple devices 120, and the correspondence between the multiple device drivers 110 and the multiple devices 120 are only examples. In actual IoT scenarios, more or fewer device drivers 110 may be included, and more or fewer devices 120 may be included. There may also be a one-to-many correspondence between the multiple device drivers 110 and the multiple devices 120. For example, the multiple devices 120 are multiple smart bulbs manufactured by the same supplier, and are matched with the same device driver 110. In one implementation, the device driver 110 includes a universal device driver. For example, the device driver 110 is a universal device driver for Bluetooth devices, which can be used to drive all different Bluetooth devices from different manufacturers.

[0026] In one embodiment, the device 120 and the corresponding device driver 110 can join one or more groups 130 according to the type of service provided. For example, the device 120 is a smart elevator, and the device 120 and the corresponding device driver 110 can join the "security control" group, the "transportation" group, and the "energy saving" group according to the type of service provided.

[0027] In one embodiment, if Figure 2 As shown, the device 120 may include multiple sub-devices 121. The multiple sub-devices 121 may be various IoT devices constituting the device 120. For example, the device 120 is a smart elevator, and the device 120 may also include multiple sub-devices 121 such as a surveillance camera, a fingerprint authenticator, an alarm device, and a smoke sensor.

[0028] In one embodiment, each sub-device 121 may also include a grandchild device ( Figure 2 For example, when the sub-device 121 is a surveillance camera, the sub-device 121 also includes sub-devices such as a proximity sensor, a motion sensor, and a light sensor.

[0029] See also Figure 3 , which is a flow chart of a device management method in one embodiment of the present invention. In this embodiment, the device management method can be applied to the device management system. Figure 3 As shown, the device management method specifically includes the following steps. According to different requirements, the order of the steps in the flowchart can be changed, and some steps can be omitted.

[0030] In step S302, the device driver 110 sends a group registration request to the management platform 100. The group registration request includes a group name, identity information and a verification key of the device driver 110, a group access permission verification key, and a group processing capability.

[0031] It should be noted that the device driver 110 can register one or more different groups. When the device driver 100 wants to register multiple different groups, it can send multiple group registration requests in batches, or it can package multiple group registration requests into one group registration request and then send it.

[0032] In step S304 , the management platform 100 verifies the legitimacy of the device driver 110 according to the identity information and the verification key of the device driver 110 .

[0033] In step S306 , the management platform 100 verifies whether the device driver 110 has group access rights according to the group name and the group access rights verification key.

[0034] In step S308, the management platform 100 feeds back the group registration request processing result to the device driver 110 according to the verification results of step S302 and step S304. When the device driver 110 is verified as legitimate through step S304 and has group access rights through step S306, the management platform 100 further performs group registration according to the group processing capability requested by the device driver 110 and feeds back the registration result to the device driver 110. The group processing capability includes: (A): obtaining event notification, (B): message broadcasting, and (C): including (A) and (B).

[0035] See also Figure 4 , which is a flow chart of a device management method executed by the management platform 100 in one embodiment of the present invention. Figure 4 As shown, the device management method specifically includes the following steps. According to different requirements, the order of the steps in the flowchart can be changed, and some steps can be omitted.

[0036] In step S402, the management platform 100 receives a group registration request sent by the device driver 110. The group registration request includes a group name, identity information and a verification key of the device driver 110, a group access right verification key, and a group processing capability.

[0037] In step S404, the management platform 100 determines whether the device driver 110 that sends the group registration request is a legitimate device driver. Specifically, the management platform 100 verifies the legitimacy of the device driver 110 based on the received identity information and verification key of the device driver 110. When the management platform 100 determines that the device driver 110 is an illegal device driver, the management platform 100 further executes step S406; when the management platform 100 determines that the device driver 110 is a legitimate device driver, the management platform 100 further executes step S408.

[0038] Step S406 : the management platform 100 rejects the group registration request of the device driver 110 .

[0039] In step S408, the management platform 100 queries the group list according to the group name to determine whether the group requested for registration already exists. When the management platform 100 determines that the group requested for registration does not exist, the management platform 100 further executes step S410; when the management platform 100 determines that the group requested for registration already exists, the management platform further executes step S412.

[0040] In this embodiment, the management platform 100 stores a group list, which includes a group name, a group status, and a device driver list corresponding to the group. The device driver list includes the identity information of each device driver registered in the group and the corresponding group processing capability.

[0041] In step S410, the management platform 100 adds the group name requested for registration, the identity information of the device driver 110, and the group processing capability to the group list. The group status is preset to be normal. In one embodiment, the management platform 100 also sends a new registered group access right verification key to the device driver 110.

[0042] Step S412: When the group requested for registration already exists, the management platform 100 further determines whether the device driver 110 has access rights to the group. Specifically, the management platform 100 may verify the access rights of the device driver 110 according to the group access verification key carried in the group registration request. When the management platform 100 determines that the device driver 110 does not have access rights to the group, step S414 is further executed; when the management platform 100 determines that the device driver 110 has access rights to the group, step S420 is further executed.

[0043] Step S414: When the device driver 110 does not have the access rights of the group, the management platform 100 notifies other device drivers in the group to obtain authorization consent from other device drivers.

[0044] In one embodiment, in step S416, the management platform 100 determines whether to obtain authorization consent from other device drivers. In one embodiment, the management platform 100 starts a timer of a preset duration when sending a notification. If no authorization consent is received from any device driver before the timer expires, step S406 is executed; if authorization consent is received from at least one other device driver before the timer expires, step S418 is executed. In one embodiment, when the management platform 100 rejects the group registration request (step S406), an error code may be transmitted at the same time. The error code corresponds to different error events, so that the device driver 110 can perform subsequent error processing.

[0045] Step S418 , after receiving at least one authorization consent, the management platform 100 accepts the group registration request and sends the group access authority verification key to the device driver 110 .

[0046] In step S420 , the management platform 100 adds the device driver 110 to the device driver list corresponding to the group, and returns a response of receiving the group registration request to the device driver 110 .

[0047] In one embodiment, upon receiving a device message from any device driver, the management platform 100 determines whether to forward the device message and the object to which the message is forwarded by querying the group list.

[0048] In one embodiment, when the management platform 100 receives a device exception message transmitted by a device driver, it queries the group list, obtains the group associated with the device driver, and modifies the group status of the group associated with the device driver to abnormal. At the same time, the management platform 100 also queries the device driver list of the group associated with the device driver to determine the group processing capability of the device driver for the associated group. When the group processing capability of the device driver for the associated group is only (A): obtaining event notification, the management platform 100 does not forward the device exception message; when the group processing capability of the device driver for the associated group is (B): message broadcast or (C): including (A) and (B), the management platform 100 forwards the device exception message, wherein the forwarding object is all other device drivers in the associated group that have the group processing capability of obtaining event notification.

[0049] For example, device driver X joins group 1, group 2, and group 3 in a registration group manner, wherein the group processing capability of group 1 is (A), and the group processing capabilities of group 2 and group 3 are both (C). When the management platform 100 receives the device exception message sent by device driver X, it queries the group list and further forwards the device exception message to all other device drivers with group processing capabilities (A) in group 2 and group 3. As for group 1, since the group processing capability of device driver X in this group is only (A), the management platform 100 will not forward the device exception message to other device drivers associated with group 1.

[0050] In one embodiment, when the management platform 100 modifies the group status to be abnormal, it also notifies the administrator of the management platform 100 so that the device abnormality / group abnormality can be processed immediately.

[0051] See also Figure 5 , shown is a schematic diagram of the structure of the management platform 100 in one embodiment of the present invention.

[0052] The management platform 100 includes at least one processor 102 and a memory 104. Those skilled in the art should understand that Figure 5 The structure of the management platform 100 shown does not constitute a limitation of the embodiments of the present application. The management platform 100 may also include more or less other hardware or software than shown in the figure, or different component arrangements.

[0053] The memory 104 stores computer program codes and is executed by at least one processor 102 to implement device management functions (see Figure 3 and Figure 4 Flowchart of the .

[0054] In some embodiments, the at least one processor 102 may be composed of an integrated circuit, such as a single packaged integrated circuit, or a plurality of packaged integrated circuits with the same or different functions, including one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and combinations of various control chips, etc. The at least one processor 102 is the control core (Control Unit) of the management platform 100, and uses various interfaces and lines to connect various components of the entire management platform 100, and executes various functions and processes data of the management platform 100 by running or executing programs or modules stored in the memory 104, and calling data stored in the memory 104, such as executing the function of device management.

[0055] In some embodiments, the memory 104 is used to store program codes and various data, and to achieve high-speed and automatic access to programs or data during the operation of the management platform 100. The memory 104 includes a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), a one-time programmable read-only memory (OTPROM), an electronically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage, magnetic tape storage, or any other computer-readable storage medium capable of carrying or storing data.

[0056] The above integrated unit implemented in the form of software function modules can be stored in a computer-readable storage medium. The above software function modules are stored in a storage medium and include several instructions for enabling a device or processor to execute parts of the methods described in various embodiments of the present invention.

[0057] The memory 104 stores program codes, and the at least one processor 102 can call the program codes stored in the memory 104 to execute related functions. For example, Figure 3 and Figure 4 The program code of the method flow is executed by the at least one processor 102, thereby realizing the functions of each module to achieve the purpose of device management.

[0058] In one embodiment, the memory 104 stores one or more instructions (ie, at least one instruction), and the at least one instruction is executed by the at least one processor 102 to achieve the purpose of device management. Figure 3 and Figure 4 shown.

[0059] In summary, the device management method, system, platform and computer-readable storage medium of the present invention provide an operation mode for device group management and message transmission in the field of Internet of Things.

[0060] Finally, it should be noted that the above embodiments are for illustration only and not limitation. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solutions of the present invention may be modified or replaced by equivalents without departing from the spirit and scope of the technical solutions of the present invention.

Claims

1. A device management method, characterized in that: The method comprises: The management platform receives a group registration request sent by the device driver, wherein the group registration request includes a group name, identity information and a verification key of the device driver, a group access right verification key, and a group processing capability; The management platform determines the legitimacy of the device driver according to the identity information and the verification key of the device driver, and when it is determined that the device driver is a legal device driver, queries the group list to determine whether the group name already exists; When it is determined that the group name does not exist, updating the group list according to the group name in the group registration request, the identity information of the device driver and the group processing capability, and presetting the group status to normal; When it is determined that the group name already exists, determining whether the device driver has group access rights according to the group access rights verification key; and When it is determined that the device driver has group access rights, the management platform adds the device driver to a device driver list corresponding to the group; When it is determined that the device driver does not have group access rights, the management platform notifies other device drivers associated with the group name to obtain authorization consent; When the management platform receives at least one authorization consent from other device drivers, it accepts the group registration request and sends the group access authority verification key to the device drivers.

2. The device management method according to claim 1, characterized in that: The method further comprises: When it is determined that the device driver is an illegal device driver, the group registration request is rejected.

3. The device management method according to claim 1, characterized in that: The method further comprises: When the preset time period expires and no authorization consent is received from the other device drivers, the group registration request is rejected.

4. The device management method according to claim 1, characterized in that: The group processing capability includes: obtaining one or both of event notification and message broadcasting.

5. A device management platform, characterized in that: The platform includes a processor and a memory, the memory is used to store at least one instruction, and the processor is used to execute the at least one instruction to implement the device management method according to any one of claims 1 to 4.

6. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one instruction, and when the at least one instruction is executed by a processor, the device management method according to any one of claims 1 to 4 is implemented.

Images