Device Management Model Generation, Device Management Method, Device, and Storage Medium

Abstract

The embodiments of the present application provide a device management model generation and device management method, device, and storage medium. In the embodiments of the present application, a user can create a target space system corresponding to a specified entity space to create a virtual management tree corresponding to the specified entity space in the target space system; further, by associating the nodes with position space attributes and logical function attributes on the virtual management tree with the entity devices in the entity space, the nodes on the virtual management tree can point to different spatial positions in the entity space and different process links in the entity space, generating a device management model that can manage entity devices from different dimensions of spatial position and logical function. Moreover, the user can obtain the generated device management model and manage the entity devices in the entity space from multiple dimensions of spatial position and logical function through the obtained device management model, and the management methods are more diverse.

Description

Technical Field

[0001] The present application relates to the field of edge cloud technology, and in particular, to a method for generating a device management model, a device management method, a device, and a storage medium. Background Art

[0002] In various manufacturing enterprises, a large number of production devices are usually involved. These production devices are important assets of the manufacturing enterprises. Therefore, it is necessary to effectively manage these device assets to reduce maintenance costs during asset construction and maintenance, reduce device downtime, and thus improve device operation efficiency and the overall production efficiency of the enterprise.

[0003] In the existing device management solutions, there is a tendency to map the physical world, that is, to associate and register each production device with the workshop to which it belongs. For example, when managing devices, a manager will record that both air compressor 1 and air compressor 2 are placed in the tenth workshop. Users can find air compressor 1 and air compressor 2 in the tenth workshop and manage them by querying this registration information. This device asset management method only supports device management from the workshop dimension and cannot meet the multi-dimensional device management requirements. Summary of the Invention

[0004] Multiple aspects of the present application provide a method for generating a device management model, a device management method, a device, and a storage medium for managing physical devices in an entity space from multiple dimensions of spatial location and logical function.

[0005] An embodiment of the present application provides a method for generating a device management model, including: in response to a creation operation of a spatial system, creating a target spatial system, where the target spatial system corresponds to a specified entity space, and the specified entity space includes multiple physical devices; in response to a generation operation of a management model, generating at least one virtual management tree in the target spatial system, where the at least one virtual management tree includes at least a first type of node with a spatial location attribute and a second type of node with a logical function attribute, different spatial location attributes correspond to different spatial locations in the specified entity space, and different logical function attributes correspond to different process links in the job processes existing in the specified entity space; combining the spatial location attributes and logical function attributes of the multiple physical devices, associating the multiple physical devices with the nodes on the at least one virtual management tree to obtain a multi-dimensional device management model.

[0006] The embodiment of the present application further provides a device management method, including: receiving a device management request, where the device management request includes a query condition, and the query condition includes at least one of a to-be-query space location attribute and a to-be-query logical function attribute; traversing at least one virtual management tree in a device management model to obtain a list of device IDs that meet the query condition, where the device management model corresponds to a specified entity space; obtaining index data of to-be-managed entity devices in the specified entity space according to the list of device IDs, and performing data analysis or management on the to-be-managed entity devices according to the index data; where the at least one virtual management tree includes at least a first type of node with a space location attribute and a second type of node with a logical function attribute, different space location attributes correspond to different space locations in the specified entity space, and different logical function attributes correspond to different process links in the job processes existing in the specified entity space; the device management model is obtained by associating the nodes on the at least one virtual management tree with multiple entity devices in the specified entity space.

[0007] The embodiment of the present application further provides a device management model generation device, including: a creation module, configured to respond to a creation operation of a space system to create a target space system, where the target space system corresponds to a specified entity space, and the specified entity space includes multiple entity devices; a first generation module, configured to respond to a generation operation of a management model to generate at least one virtual management tree in the target space system, where the at least one virtual management tree includes at least a first type of node with a space location attribute and a second type of node with a logical function attribute, different space location attributes correspond to different space locations in the specified entity space, and different logical function attributes correspond to different process links in the job processes existing in the specified entity space; a second generation module, configured to combine the space location attributes and logical function attributes of the multiple entity devices to associate the multiple entity devices with the nodes on the at least one virtual management tree to obtain a multi-dimensional device management model.

[0008] The embodiment of the present application further provides a device management apparatus, including: a receiving module, configured to receive a device management request, where the device management request includes a query condition, and the query condition includes at least one of a to-be-query spatial location attribute and a to-be-query logical function attribute; a query module, configured to traverse at least one virtual management tree in a device management model to obtain a list of device IDs that meet the query condition, where the device management model corresponds to a specified entity space; a management module, configured to obtain index data of entity devices to be managed in the specified entity space according to the list of device IDs, so as to perform data analysis or management on the entity devices to be managed according to the index data; where the at least one virtual management tree includes at least a first type of node with a spatial location attribute and a second type of node with a logical function attribute, different spatial location attributes correspond to different spatial locations in the specified entity space, and different logical function attributes correspond to different process links in the job processes existing in the specified entity space; the device management model is obtained by associating nodes on the at least one virtual management tree with multiple entity devices in the specified entity space.

[0009] The embodiment of the present application further provides an edge computing device, including: a display, a processor, and a memory storing a computer program, where the processor is configured to execute the computer program to perform any one of the steps in the method.

[0010] The embodiment of the present application further provides a computer-readable storage medium storing a computer program, where when the computer program is executed by a processor, the processor is caused to implement any one of the steps.

[0011] The embodiment of the present application further provides a computer program product, including computer program / instructions, where when the computer program / instructions are executed by a processor, the processor is caused to implement any one of the steps in the method.

[0012] In the embodiment of the present application, a user can create a target space system corresponding to a specified entity space to create a virtual management tree corresponding to the specified entity space in the target space system; further, by associating nodes with spatial location attributes and logical function attributes on the virtual management tree with entity devices in the entity space, the nodes on the virtual management tree can point to different spatial locations in the entity space and different process links in the entity space, generating a device management model that can manage entity devices from different dimensions of spatial location and logical function. And the user can obtain the generated device management model and manage the entity devices in the entity space from multiple dimensions of spatial location and logical function through the obtained device management model, and the management methods are more diverse. Description of the Drawings

[0013] The accompanying drawings described herein are used to provide a further understanding of the present application and form a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation of the present application. In the drawings:

[0014] Figure 1 is a flowchart of a method for generating a device management model provided by an embodiment of the present application;

[0015] Figure 2a is a schematic diagram of a service page for creating a target space system provided by an embodiment of the present application;

[0016] Figure 2b is a schematic diagram of a space system page for displaying a basic tree provided by an embodiment of the present application;

[0017] Figure 2c is a schematic diagram of an editing interface for editing a basic tree provided by an embodiment of the present application;

[0018] Figure 2d is a schematic diagram of a basic tree after editing provided by an embodiment of the present application;

[0019] Figure 2e is a schematic diagram of an operation interface for exporting a space system provided by an embodiment of the present application;

[0020] Figure 3a is a flowchart of a device management method provided by an embodiment of the present application;

[0021] Figure 3b is a flowchart of another method for generating a device management model provided by an embodiment of the present application;

[0022] Figure 4 is a schematic diagram of the structure of a device management model generation device provided by an embodiment of the present application;

[0023] Figure 5 is a schematic diagram of the structure of a device management device provided by an embodiment of the present application;

[0024] Figure 6 is a schematic diagram of the structure of an edge computing device provided by an embodiment of the present application. Detailed Embodiments

[0025] To make the objectives, technical solutions, and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below in conjunction with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the scope of protection of the present application.

[0026] In the process of production enterprises managing production equipment, the physical world mapping method is usually adopted to associate and register each production equipment with the workshop to which it belongs, so as to determine the ownership relationship between each production equipment and each workshop in the physical space, and then realize the management and maintenance of the production equipment in each workshop. However, considering only from the dimension of the physical space cannot well meet the management requirements of a large number of production equipment. In the enterprise production scenario, the production structure usually involves factories, workshops, workstations, production lines / processes, and the production equipment used in each process on the production line / process. In order to more clearly understand information such as the operating status and resource consumption of production equipment, it is not only necessary to know the workshop to which each production equipment belongs, but in more cases, it is necessary to understand the corresponding operating status, resource consumption, etc. of each production equipment in the current process from dimensions such as production lines / processes. Therefore, combined with the actual management requirements of production enterprises, it is necessary to provide a solution that can manage production equipment from both the physical spatial location dimension and the logical function dimensions such as production lines / processes.

[0027] For this reason, in the embodiments of the present application, a new device management model is provided. This device management model supports the management of entity devices in various industries from multiple dimensions, and can manage entity devices from the spatial location dimension with different granularities, and can also manage entity devices from the logical function dimension with different granularities. The device management model provided by the embodiments of the present application can be applied to various industries that involve entity devices that need to be managed, such as various production industries, or the logistics industry, the warehousing management industry, etc. The entity devices in the embodiments of the present application refer to the physical devices that need to be managed in various industries. According to the different application industries, these entity devices will also be different. Taking the production industry as an example, these entity devices can be various production equipment. Further taking the garment industry as an example, these entity devices involve production equipment such as cloth cutting machines, ironing machines, printing machines, and sewing machines. Taking the logistics industry as an example, these entity devices involve various logistics equipment such as sealing equipment, labeling equipment, loading and unloading equipment, handling robots, and goods transportation equipment.

[0028] Further, to facilitate multi-dimensional management of physical devices in various industries through the new device management model, an embodiment of the present application may provide an edge computing device, which is responsible for generating the new device management model and performing device management based on the device management model. The edge computing device provided by the embodiment of the present application is a computing device with capabilities such as computing, networking, storage, and security that can be deployed at the edge of the cloud network. In terms of implementation form, the edge computing device can be implemented as one or more servers and software programs deployed on the servers, and these servers and software programs can be packaged together as a cloud product in an edge deployment form (i.e., the edge computing device) and provided to enterprise users. In the edge computing device, by running the corresponding software programs, a device management model generation service and a device management service based on the generated device management model can be provided to enterprise users. Enterprise users can deploy the edge computing device in the enterprise on-site environment or in the computer room or Internet Data Center (IDC) of the edge cloud system close to the enterprise on-site environment, and there is no limitation on this. Regardless of the deployment location, enterprise users can generate a device management model adapted to their application requirements through the device management model generation service provided by the edge computing device, and can manage various physical devices within the enterprise from multiple dimensions such as spatial locations and logical functions at different granularities. In the following embodiments of the present application, the generation process of the device management model and the device management process based on the device management model will be described in detail.

[0029] An embodiment of the present application provides a method for generating a device management model. Through this method, a device management model capable of managing physical devices from multiple dimensions can be generated for developers or front-line operators in various industries to manage relevant physical devices. Figure 1 The flowchart of the method for generating a device management model provided by the embodiment of the present application is as Figure 1 shown, and the method includes:

[0030] S1. In response to the creation operation of the spatial system, create a target spatial system, where the target spatial system corresponds to a specified physical space, and the specified physical space includes multiple physical devices;

[0031] S2. In response to the generation operation of the management model, generate at least one virtual management tree in the target spatial system. The at least one virtual management tree includes at least a first type of node with a spatial location attribute and a second type of node with a logical function attribute. Different spatial location attributes correspond to different spatial locations in the specified physical space, and different logical function attributes correspond to different process links in the job processes existing in the specified physical space;

[0032] S3. Combine the spatial location attributes and logical function attributes of multiple physical devices, and associate the multiple physical devices with nodes on at least one virtual management tree to obtain a multi-dimensional device management model.

[0033] In this embodiment, the concept of a spatial system is proposed. A spatial system is a logical management space that can be defined by the user according to their own management needs. Suppose the user has management requirements for the physical devices in a specified physical space. Then, a corresponding spatial system can be established for the specified physical space. As a logical management space, this spatial system can carry the spatial locations in the specified physical space that are adapted to the user's management needs, the operation processes in the specified physical space that are adapted to the user's management needs, and the process links in the operation processes. Further, it can also carry the association relationships between these spatial locations and process links to form a virtual management tree. Among them, these spatial locations and process links that are adapted to the user's management needs can also be referred to as spatial resources or resource objects in the spatial system. If the user has management requirements for the physical devices in different physical spaces, different spatial systems can be created for different physical spaces. Each spatial system has a unique identifier. Optionally, the unique identifier of the spatial system can be called the system code (SystemCode). The user can query the corresponding spatial system through the system code.

[0034] In the embodiment of the present application, after the device management model generation service is deployed and started, as Figure 2a shown, a service page can be displayed. On this service page, there is a function control for creating a spatial system, so that the user can initiate an operation to create a spatial system when needed. When the user has management requirements for the physical devices in a specified physical space, the user can initiate a spatial system creation operation through this function control. Correspondingly, in response to the user triggering this function control, a spatial system corresponding to the specified physical space can be created, and the created spatial system can be rendered to the area below the function control. For the convenience of description and distinction, in this embodiment, the spatial system corresponding to the specified physical space is called the target spatial system. In the embodiment of the present application, the specific type of the specified physical space is not limited. According to different application industries, the corresponding physical spaces will also be different. For example, in the manufacturing industry, the specified physical space can be a factory, a workshop, or multiple workshops or multiple factories, etc.; for another example, in the warehousing and logistics industry, the specified physical space can be a warehouse, etc. For example, when all the physical devices in a factory need to be managed, the specified physical space is a factory; when all the physical devices in a certain workshop or several workshops in a factory need to be managed, the specified physical space is a workshop or several workshops; when all the physical devices in multiple factories across different regions need to be managed, the specified physical space is multiple factories across different regions, etc.

[0035] After obtaining the target space system, at least one virtual management tree can be generated in the target space system, and entity devices in the specified entity space can be managed through nodes on these virtual management trees. Each virtual management tree has a unique identifier. Optionally, the unique identifier of the virtual management tree can be referred to as the space code (spaceCode), and the user can query the corresponding virtual management tree through the space code. Specifically, at least one virtual management tree can be generated in the target space system in response to the generation operation of the management model. In the embodiments of the present application, in order to manage entity devices from multiple dimensions, the virtual management tree in the target space system includes at least two types of nodes, namely, the first type of nodes with spatial location attributes and the second type of nodes with logical function attributes. In this embodiment, the spatial location attribute and the logical function attribute are two major types of attributes, and different granularity attributes can also be included under each attribute. That is to say, from the perspective of attribute granularity, there are multiple spatial location attributes and multiple logical function attributes; further, at the same granularity, there can be multiple spatial location attributes and multiple logical function attributes. For example, the factory is a granularity, and the workshop is a granularity. At the factory granularity, there can be Factory 1 - Factory n, and at the workshop granularity, there can be Workshop 1 - Workshop m; similarly, the production line is a granularity, and the process is a granularity. At the production line granularity, there can be Production Line 1 - Production Line k, and at the process granularity, there can be Process 1 - Process p. Among them, n, m, k, and p are all natural numbers greater than or equal to 2. It should be noted that these attribute granularities and the attribute divisions at the same granularity are divided according to the management needs of the user, and may be the same as or different from the granularity and quantity of the position space and the production line and process in actual production.

[0036] In an embodiment of the present application, the number of first-class nodes is one or more, and in the case of multiple nodes, the spatial position attributes corresponding to different first-class nodes may be the same or different; similarly, the number of second-class nodes is one or more, and in the case of multiple nodes, the logical function attributes corresponding to different second-class nodes may be the same or different. Among them, different spatial position attributes correspond to different spatial positions in the specified physical space, that is, the first-class nodes corresponding to different spatial position attributes represent different spatial positions in the physical space. For example, there are two nodes with different spatial position attributes, one node represents workshop 1, and the other node may represent workshop 2, or one node represents workshop 1, and the other node represents factory 1. Correspondingly, different logical function attributes correspond to different process links in the operation process existing in the specified physical space, that is, the second-class nodes corresponding to different logical function attributes represent different process links. For example, there are two nodes with different logical function attributes, one node represents process 1, and the other node may represent process 2, or one node represents production line 1, and the other node may represent process 2.

[0037] In addition, the embodiment of the present application does not limit the number of virtual management trees included in the target space system, which can be one or more. In particular, in the case where the target space system includes one virtual management tree, the virtual management tree includes two types of nodes at the same time, that is, it includes both first-type nodes and second-type nodes, and is a hybrid tree that has both spatial location attributes and logical function attributes. In the case where the target space system includes two or more virtual management trees, there are the following two situations:

[0038] Case 1: These virtual management trees include a first-type management tree and a second-type management tree; wherein, all nodes on the first-type management tree are first-type nodes, and all nodes on the second-type management tree are second-type nodes.

[0039] Case 2: All of these virtual management trees are third-type management trees, that is, the third-type management trees have both first-type nodes and second-type nodes.

[0040] Case 3: These virtual management trees include the first type of management tree, the second type of management tree and the third type of management tree.

[0041] In any of the above cases, the device management requirements of the user can be obtained. According to the device management requirements, combined with the attributes of each node on the virtual management tree, as well as the spatial location attributes and logical function attributes of multiple entity devices in the specified entity space, multiple entity devices are associated with the nodes on at least one virtual management tree, and finally a multi-dimensional device management model is obtained. In this embodiment, each entity device has both spatial location attributes and logical function attributes, and these spatial location attributes and logical function attributes are also granular and there will be multiple different attributes at the same granularity. For example, in one case, the device management requirement is to manage the devices with the first spatial location attribute, then the entity devices with the first spatial location attribute can be associated with the nodes with the first spatial location attribute; in another case, the device management requirement is to manage the entity devices with the first logical function attribute on the first spatial location attribute, then the entity devices with the first logical function attribute on the first spatial location attribute can be associated with the nodes with the first logical function attribute. For example, if the device management requirement is to manage device A in workshop 1, then the node with the spatial location attribute of workshop 1 can be associated with device A; in another case, the device management requirement is to manage the entity devices with the first logical function attribute on the first spatial location attribute, then the entity devices with the first logical function attribute on the first spatial location attribute can be associated with the nodes with the first logical function attribute. For example, if the device management requirement is to manage device B responsible for the printing process in workshop 2, then the node with the logical function attribute of the printing process can be associated with device B, and so on.

[0042] In the embodiment of the present application, the user can create a target space system corresponding to the specified entity space through the edge device deployed with the device management model generation service, so as to create a virtual management tree corresponding to the specified entity space in the target space system; further, by associating the nodes with the location space attributes and logical function attributes on the virtual management tree with the entity devices in the entity space, the nodes on the virtual management tree can point to different spatial locations in the entity space and point to different process links in the entity space, generating a device management model that can manage entity devices from different dimensions of spatial location and logical function. And the edge device also provides a device management service. Based on this device management service, the user can obtain the generated device management model and manage the entity devices in the entity space from multiple dimensions of spatial location and logical function through the obtained device management model, and the management methods are more diverse.

[0043] In the embodiment of the present application, the specific manner of creating the target space system is not limited. Optionally, in response to the user's triggering operation on the "Create Space System" function control on the service page, such asFigure 2b As shown, a space system page can be displayed, and at least one basic tree can be created on this space system page; among them, at least one basic tree and the space system page form the target space system of this embodiment. That is to say, the target space system of this embodiment is a page with management functions in specific implementation, and there is at least one basic tree on this page. In the embodiments of this application, as Figure 2b shown, each basic tree can include a root node and at least one level of child nodes with empty attributes. It should be noted that the embodiments of this application do not limit the specific structure of at least one basic tree. At least one basic tree can have exactly the same structure, that is, having the same node levels and including the same number of nodes on each level, or can have different structures; among them, the nodes on each basic tree have corresponding attributes, but in the initial stage, the attributes of each node are empty. In addition, it should be noted that in the embodiments of this application, the number of basic trees is not limited either. In different space systems, the number of basic trees can be the same or different. In addition, users are allowed to delete or add these basic trees. Specifically, as Figure 2b shown, in the space system page, the area where the basic tree is located contains an "Add" control and a "Delete" control. When the user triggers the "Add" control, a new basic tree can be added in the area where the basic tree is located, and when any basic tree is selected, triggering the "Delete" control can delete the selected basic tree. Further optionally, during the process of adding a basic tree, a basic tree setting page can also be displayed, and the user can set the structure information of the basic tree through this basic tree setting page, that is, the user can set the number of layers of the basic tree, the number of nodes included in each layer, and the parent-child relationship between nodes, etc., and then generate a new basic tree according to the structure information of the basic tree set by the user and present it on the space system page.

[0044] In the embodiments of this application, these basic trees are the basis for generating virtual management trees, and editing of these basic trees is allowed to generate corresponding virtual management trees. Optionally, the user can perform an editing operation on the basic trees in the target space system to generate a virtual management tree on the basis of the basic trees. In an optional embodiment, these basic trees in the target space system support interactive operations, and the user can trigger at least one basic tree to edit it to generate a corresponding virtual management tree. In another optional embodiment, an editing control is displayed in the area where each basic tree is located, and the user can initiate an editing operation on a certain basic tree by triggering this editing control. Here it is explained that in the embodiments of this application, no matter whether the object triggered by the user is a page, a basic tree or a control, the triggering method can adopt but is not limited to any one of the following: click, double-click, long press, touch, mouse hover, etc. Based on this, in response to the editing trigger operation initiated by the user on any basic tree, when responding to the situation of triggering the editing operation on any basic tree, as Figure 2cAs shown, an editing interface corresponding to the base tree to be edited can be displayed, and the base tree is rendered onto the editing interface to obtain the tree to be edited; among them, the process of rendering the base tree onto the editing interface includes: rendering a canvas on the display screen, which provides basic interaction tools such as full-screen and zooming, and these basic interaction tools are located in the tool area. The canvas also includes an editing area; then, according to the structure of the base tree, that is, the parent-child relationship (or called hierarchical relationship) between the root node and each level of child nodes, starting from the root node recursively, nodes are rendered one by one in the editing area according to the hierarchy; during this process, in order to facilitate the user to perform editing operations on the base tree, the editing events corresponding to the preset editing operations can be bound to each node, such as click events, drag events, etc. After binding the editing events, the nodes support the user to perform corresponding editing operations on them. For example, the user can perform click or drag operations on the nodes. In this embodiment, for the same tree (including the base tree, the tree to be edited, or the virtual management tree), the nodes other than the root node are called child nodes.

[0045] Among them, the base tree on the editing interface is in an editable state, so it is called the tree to be edited. After the user performs various editing operations on the tree to be edited, a virtual management tree can be obtained. The user can trigger any child node to perform an editing operation. Optionally, the events bound to the child node include but are not limited to property setting events, node addition events, node deletion events, and dragging events, etc. These editing events correspond to different editing operations. Through different editing operations, different types of editing operations can be performed on the child node. For example, for any child node, the property setting event can be triggered through the property editing operation to edit the properties of the child node, or the node addition event can be triggered through the node addition operation to add subordinate child nodes to the child node, or the node deletion event can be triggered through the node deletion operation to delete the child node, or the dragging event can be triggered through the dragging operation to adjust the parent-child relationship between the child node and other child nodes or the root node, etc. These editing operations or events will generate the latest child nodes and their properties and hierarchical relationships. Based on this, in response to the user's editing operation on the tree to be edited, the latest child nodes and their properties and hierarchical relationships generated by the editing operation can be obtained, and a virtual management tree can be generated according to the latest child nodes and their properties and hierarchical relationships.

[0046] In the embodiments of the present application, the types of editing operations that can be performed on each child node in the tree to be edited by the user and the specific ways of performing the editing operations are not limited. Optionally, the editing operation can be at least one of adding a child node, setting the attributes of a child node, deleting a child node, and adjusting the hierarchical relationship of child nodes; further optionally, when the user performs any of the above operations on a child node in the tree to be edited, any child node can be triggered to trigger a corresponding event, so that when the corresponding type of event is responded to, the corresponding type of editing operation is performed. For example, in response to the user's operation of setting the attributes of any child node in the tree to be edited, the corresponding attribute setting event of the child node can be triggered to display an attribute setting interface; further, the user can input the attribute information corresponding to the child node in this attribute setting interface, and then in response to the user's input operation on this attribute setting interface, the attributes of the child node can be obtained. For another example, in response to the user's operation of adding a node to any child node in the tree to be edited, the corresponding node addition event of the child node can be triggered to add a next-level child node under the child node. Figure 2d is a schematic diagram after adding next-level child nodes respectively under two child nodes of the base tree, as Figure 2d shown. The next-level child nodes of the root node of this base tree are child node 1, child node 2, and child node 3 respectively. The user adds next-level child nodes 11, 12, and 13 under child node 1 respectively, and adds next-level child nodes 31 and 32 under child node 3. Further, the user can also perform an operation of setting the attributes of the newly added next-level child nodes to set their attributes; based on this, in response to the user's operation of setting the attributes of the next-level child nodes, the corresponding attribute setting event of the next-level child nodes can be triggered to display an attribute setting interface; further, the user can input the attribute information corresponding to the next-level child nodes in this attribute setting interface, and then in response to the user's input operation on this attribute setting interface, the attributes corresponding to the next-level child nodes can be obtained. For another example, in response to the user's operation of deleting any child node in the tree to be edited, the corresponding node deletion event of the child node can be triggered to delete the child node and its attributes, and when the child node has lower-level child nodes, delete the lower-level child nodes and their attributes of the child node. For another example, in response to the user's operation of dragging any child node in the tree to be edited, the corresponding drag event of the child node can be triggered; further, according to the target position where the child node is dragged to, the latest parent node and / or child node of the child node can be determined, and the hierarchical relationship of the child node can be modified according to the latest parent node and / or child node.

[0047] In the embodiments of the present application, the specific manner of performing the above editing operations is not limited. Optionally, when any child node is triggered, a function list can be displayed in the form of a pop-up window or a floating layer. The list may include function labels such as "attribute setting", "node addition", "node deletion", or "node adjustment". The user can trigger any label to initiate the corresponding editing operation. For example, when the user triggers "attribute setting", an attribute setting interface can be displayed for the user to input the attribute information of the node. When the user triggers the "node addition" label, a next-level child node can be added to the current child node. When the user triggers the "node deletion" label, the current child node and its attributes can be deleted, or the current child node and its lower-level child nodes and their attributes can be deleted together. When the user triggers the "node adjustment" label, the current child node becomes draggable. The user can drag the current node to the next level of any child node or the root node as its child node, and modify the hierarchical relationship of the child node according to the latest parent node and / or child nodes. Of course, the above editing methods are only illustrative and are not limited thereto. When the child nodes in the tree to be edited support direct editing operations, the user can directly trigger any child node to initiate the corresponding editing operation. For example, when it is detected that the user clicks on any child node, a next-level child node can be automatically added to it. When it is detected that the user double-clicks on any child node, the child node can be directly deleted, or the current child node and its lower-level child nodes and their attributes can be deleted together. The child node is by default draggable. The user can directly drag the current child node to the next level of any child node or the root node as its child node, and modify the hierarchical relationship of the child node according to the latest parent node and / or child nodes. For another example, when any child node is selected, a next-level child node can be added to the selected child node or the selected child node can be deleted by using a shortcut key, etc. Of course, the tree to be edited can also be edited in any combination of the above two or more ways to generate a corresponding virtual management tree, which can be specifically determined according to actual needs and is not limited herein.

[0048] It should be noted here that the attributes of the child nodes on the same layer of a tree to be edited can be spatial location attributes at a certain granularity, logical function attributes at a certain granularity, or some child nodes can be spatial location attributes at a certain granularity while some other child nodes can be logical function attributes at a certain granularity. The attribute types of the child nodes on the same layer can be the same or different. Which attribute to set for each child node and at which granularity can be determined according to management requirements specifically, and no restrictions are imposed here. For example, assume that the first layer has two child nodes. Set one of the child nodes on the first layer to have a spatial location attribute, and its specific spatial location attribute is Workshop 1. Set the other child node on the first layer to have a spatial location attribute, and its specific spatial location attribute is Workshop 2. Further, logical function attributes can be set for the child nodes on the second layer. Assume that logical function attributes are set for the child nodes at the next level of the child node of Workshop 1, and its specific logical function attribute is Process 1 corresponding to Production Line 1. Set logical function attributes for the child nodes at the next level of the child node of Workshop 2, and its specific logical function attribute is Process 2 corresponding to Production Line 2. Another example, assume that the first layer has two child nodes. Set one of the child nodes on the first layer to have a spatial location attribute, and its specific spatial location attribute is Workshop 1. Set the other child node on the first layer to have a logical function attribute, and its specific logical function attribute is Process 1 corresponding to Production Line 1. Further, logical function attributes can be set for the child nodes at the next level of the child node of Workshop 1, and its specific logical function attribute is Process 2 corresponding to Production Line 2. Set spatial location attributes for the child nodes at the next level of the child node of Process 1, and its specific spatial location attribute is Workshop 2, and so on.

[0049] In the embodiments of the present application, the generated virtual management tree is not mapped according to the actual positions of the specified entity spaces in the physical world, but is obtained based on the spatial positions and logical functions corresponding to the entity devices used in the factories, workshops, production lines / processes, and each process on the production lines / processes of the enterprise. Therefore, at least one virtual management tree in the target space system includes at least two types of nodes, namely, two types of nodes with spatial position attributes or logical function attributes. According to the types of nodes, the virtual management tree can be classified. In the embodiments of the present application, when classifying the virtual management tree, the focus is on the child nodes and the root node is not considered. Based on this, a virtual management tree in which all child nodes have spatial position attributes is called a first type of management tree, a virtual management tree in which all child nodes have logical function attributes is called a second management tree, and a virtual management tree in which some child nodes have spatial position attributes and some child nodes have logical function attributes is called a third type of management tree. Further, the embodiments of the present application do not limit the number and types of virtual management trees. Optionally, when there are multiple virtual management trees, the multiple virtual management trees may include the first type of management tree and the second type of management tree, or all the multiple virtual management trees are of the third type; when there is one virtual management tree, the virtual management tree is of the third type. For any virtual management tree, the hierarchical relationship between child nodes reflects the hierarchical relationship or cascade relationship between the attributes of each layer of child nodes. The child nodes of the same layer have one or both of spatial position attributes and logical function attributes, and the same type of attribute can have one or more. Regarding the specific structure of each virtual management tree, it can be determined according to the spatial positions and logical functions corresponding to the entity devices used in the factories, workshops, production lines / processes, and each process on the production lines / processes of the enterprise. In this way, by using the generated virtual management tree as the equipment management model for the enterprise to manage factories, workshops, production lines / processes, and entity devices, it is convenient and intuitive to understand the usage status of entity devices from the perspective of the production line / process.

[0050] In the embodiments of the present application, the number of spatial position attributes and logical function attributes corresponding to child nodes in each virtual management tree is not limited. Optionally, both the spatial position attributes and the logical function attributes can be one or more. In the case where there are multiple spatial position attributes, each spatial position attribute corresponds to a spatial position in a specified entity space, and different spatial position attributes correspond to different spatial positions. Of course, the first type of nodes with the same spatial position attribute correspond to the same spatial position in the specified entity space, and the first type of nodes with different spatial position attributes correspond to different spatial positions in the specified entity space. For example, if device 1 and device 2 are both located in workshop A, then the child nodes 1 and 2 associated with device 1 and device 2 respectively are both the first type of nodes and correspond to the same spatial position, which is workshop A. Another example, if device 3 is located in workshop B and device 4 is located in workshop C, then the child nodes 3 and 4 associated with device 3 and device 4 respectively are both the first type of nodes, but correspond to different spatial positions, which are workshop B and workshop C respectively. In the case where there are multiple logical function attributes, each logical function attribute corresponds to a process step in the operation process in the specified entity space, and different logical function attributes correspond to different process nodes in the operation process in the specified entity space. Of course, the second type of nodes with the same logical function attribute correspond to the same process step in the operation process in the specified entity space, and the second type of nodes with different logical function attributes correspond to different process steps in the operation process in the specified entity space. For example, if device 1 and device 2 are both devices responsible for the printing process in a printing production line, then the child nodes 1 and 2 associated with device 1 and device 2 respectively are both the second type of nodes with the printing logical function attribute and correspond to the same process node, which is the printing process. Another example, if device 3 is a device responsible for the tracing process in a printing production line and device 4 is a device responsible for the cutting process in a printing production line, then the child node 3 associated with device 3 is the second type of node with the tracing logical function attribute, and the corresponding process step is the tracing process, and the child node 4 associated with device 4 is the second type of node with the cutting logical function attribute, and the corresponding process step is the cutting process. It should be noted that the segmentation granularity of the process steps in the embodiments of the present application is determined according to the device management requirements, and may be the same as or different from the process joints in the actual operation process, which is not limited here.

[0051] In the embodiments of the present application, each child node on the virtual management tree can also be bound with a device association event for the user to associate the child node in the virtual management tree with an entity device; further optionally, the child node in the virtual management tree also corresponds to a device asset list, which contains the identifiers of the entity devices associated with the child node. For each child node, when the user associates an entity device with it, the identifier of the associated entity device will be added to the device asset list corresponding to the current child node. Based on this, when associating multiple entity devices with the nodes on at least one virtual management tree in combination with the spatial location attributes and logical function attributes of the multiple entity devices, an association trigger operation can be performed for each child node on each virtual management tree to trigger the device association event corresponding to the child node; based on this, in response to the association trigger operation for the child node, the device association event can be triggered and the attributes and device association interface of the child node can be displayed. The device association interface includes at least one input item for the user to input the identifier of the target entity device. Further, in response to the input operation on the device association interface, the identifier of the target entity device to be associated with the child node can be obtained and added to the device asset list of the child node; wherein, the target entity device has attributes adapted to the child node, that is, the spatial location or logical function corresponding to the target entity device is adapted to the attributes of the child node. For example, if the child node is a first type of node, that is, the child node has a spatial location attribute, the corresponding attribute value of the child node is the spatial location corresponding to the target entity device in the workshop; for another example, if the child node is a second type of node, that is, the child node has a logical function attribute, the corresponding attribute value of the child node is the process link corresponding to the target entity device in the production line / process. For the optional manner of performing the device association operation on the child node in the virtual management tree, reference can be made to the above manner of performing other operations on the child node, which will not be elaborated here.

[0052] In the embodiment of the present application, when adding the identifier of the target entity device to the device asset list of the child node, it is possible to determine whether the target entity device has attributes adapted to the child node according to the identifier of the target entity device. If it is determined that the target entity device does not have such attributes, a prompt message can be output for the user to confirm whether to establish an association relationship between the child node and the target entity device. Optionally, the prompt message can be output in the form of a pop-up window or a floating layer. The prompt message interface includes controls for performing confirmation operations and cancellation operations to determine whether to establish an association relationship between the child node and the target entity device. If the user determines to establish an association relationship between the child node and the target entity device, a trigger operation can be performed on the confirmation control, and a confirmation association instruction can be sent to the system. Further, in the case of receiving the confirmation association instruction, an association relationship can be established between the child node and the target entity device, and the identifier of the target entity device can be added to the device asset list of the child node. If the user determines not to establish an association relationship between the child node and the target entity device, a trigger operation can be performed on the cancellation control, and a cancellation association execution can be sent to the system, then the association relationship between the child node and the target entity device is not established.

[0053] In the embodiment of the present application, when determining whether the target entity device has attributes adapted to the child node according to the identifier of the target entity device, the specific method of obtaining the attributes of the target entity device is not limited. Optionally, the attribute information of the target entity device can be obtained in real time according to the identifier of the target entity device. For example, an attribute information acquisition instruction can be sent to the target entity device in real time for the target entity device to return the corresponding attribute information. In another alternative embodiment, an attribute information input function can also be provided when associating the child node in the virtual management tree with the target entity device to obtain the input attribute information. For example, in response to the user performing an association trigger operation, a device association interface is displayed. The device association interface also includes an attribute input item for the user to input the attribute information of the target device. Further optionally, when it is determined that the target entity device does not have attributes adapted to the child node, if a trigger operation is performed on the confirmation control in response to the user, an attribute information input interface can also be displayed for the user to input the attribute information of the target entity device. Further, in response to the user's input operation on the attribute information editing interface, the attribute information of the target entity device can be obtained. And in response to the user determining the end of the input, an association relationship between the target entity device and the child node can be established, and the attributes of the target entity device and the child node can be associated together, and the identifier of the target entity device can be added to the device asset list corresponding to the child node.

[0054] In the case of associating the child nodes in the virtual management tree with the target entity device, a device management model for managing the entity device is obtained. Further, after obtaining the device management model, a device management request can be received, where the device management request includes a query condition, and the query condition includes at least one of a to-be-query space location attribute and a to-be-query logical function attribute. Based on this, when the device management request is received, at least one virtual management tree in the device management model can be traversed according to the to-be-query space location attribute and / or the to-be-query logical function attribute in the query condition to obtain a device ID list that meets the query condition. Further, the metric data of the entity device to be managed in the specified entity space can be obtained according to the device ID list, so as to perform data analysis or management on the entity device to be managed based on the metric data. In the embodiments of the present application, the specific manner of obtaining the metric data of the entity device to be managed in the specified entity space according to the device ID list is not limited. Optionally, a metric data acquisition request can be sent to the corresponding entity device according to the device ID in the device ID list for the entity device to return the corresponding metric data; for example, an SQL statement for reading metric data can be sent to the entity device for the entity device to execute the SQL statement to read and return the corresponding metric data. In another alternative embodiment, data modeling for the corresponding entity device can also be obtained by training in advance according to the metric data of each entity device. When the device ID list is determined, the metric data in the corresponding data model can be read according to each device ID in the device ID list; among them, the metric data of the entity device includes, but is not limited to, the power consumption, the number of shutdowns, the shutdown duration, etc. of the entity device. Based on this, when the metric data of the entity device to be managed is obtained, the operating state of the entity device to be managed can be analyzed according to the metric data, and corresponding processing can be performed when the operating state is determined to be abnormal.

[0055] In the embodiments of the present application, the embodiments of the present application also provide a space system export function, such as Figure 1As shown, the function controls on the space system page further include a space system export control. When the user selects the target system space, the space system export control can be triggered to export the selected target system space, the information of multiple entity devices associated with the virtual management tree therein, and the cascading relationship between each entity device. Since when creating the target space system and creating a virtual management tree in the target space system, a unique system identifier (SystemCod) is created for each target system space, a unique space identifier (SpaceCode) is created for the root node of each virtual management tree, and a unique node identifier is created for each sub-node in each virtual management tree. Based on this, in response to the space system export control being triggered, the space identifier corresponding to the root node of all virtual management trees corresponding to the selected target system space can be queried according to the system identifier of the selected target system space; then, according to the cascading relationship between the root node and the sub-nodes in each virtual management tree, the node identifiers corresponding to all sub-nodes in each virtual management tree can be queried; based on this, the device identifier associated with each sub-node can be obtained according to the association relationship between each sub-node and the entity device, so as to obtain the relevant information of the entity device according to the device identifier. In the embodiments of the present application, the file type and the specific form of the file content are not limited. Optionally, it can be exported in the form of an Excel table, and the Excel table includes the identifiers corresponding to entity devices at each level; in another optional embodiment, it can also be exported in the form of a document, and the document includes a tree diagram corresponding to the structure of the virtual management tree, and each node in the diagram is the identifier of the corresponding entity device. Of course, the above export form and export content are only exemplary descriptions and are not limited thereto. Optionally, the export content may further include the name, attribute information, and index data of the entity device, etc., which can be specifically determined according to actual needs.

[0056] Further optionally, when exporting the target space system, it is also possible to select to export the content of the target space system according to different dimensions, so as to export all or part of the content in the target space system. Figure 2e A schematic diagram for exporting the target space system according to different dimensions is as follows Figure 2e As shown, before the user determines to export the target space system, the export type can be selected. Assume that export dimension 1 is to export by factory dimension, export dimension 2 is to export by workshop dimension, and export dimension 3 is to export by production line dimension. Based on this, the user can select any export dimension as needed to export the corresponding content in the target space system in the form of Excel or a document. For example, if the user selects to export by workshop dimension, then when the confirmation control is triggered, the content corresponding to each workshop in the target system can be exported in the form of Excel or a document. Of course, in actual applications, it is not limited thereto, and different export dimensions can also be implemented, which can be specifically determined according to actual needs.

[0057] In addition to the space system export function, the embodiments of the present application also provide a space system import function. For example, Figure 2a as shown, the function controls on the space system page further include a space system import control. The user can trigger the space system import control to import a file pre-storing the content of the target space system into the edge computing device. When the file is imported into the edge computing device, a corresponding target space system is created in the service page, and the corresponding virtual management tree in the file is rendered in the target space system. Based on this, when the user's trigger of the space system import control is responded to, a file import window can be displayed, and the user can import an existing file into the edge computing device through the file import window. When the edge computing device obtains the imported file, it can read the content in the file and create a corresponding target space system in the service page according to the content in the file, and render the corresponding virtual management tree in the target space system for the user to manage the associated devices through the virtual management tree.

[0058] Based on the above, the embodiments of the present application also provide a device management method to obtain the index data of physical devices from multiple dimensions through the device management model in the above embodiments for data analysis and management of physical devices. Figure 3a The flowchart of the device management method provided by the embodiments of the present application is as follows. Figure 3a As shown, the method includes:

[0059] P1. Receive a device management request, where the device management request includes a query condition, and the query condition includes at least one of a to-be-query space location attribute and a to-be-query logical function attribute;

[0060] P2. Traverse at least one virtual management tree in the device management model to obtain a list of device IDs that meet the query conditions. The device management model corresponds to a specified physical space;

[0061] P3. Obtain the index data of the physical devices to be managed in the specified physical space according to the list of device IDs, and perform data analysis or management on the physical devices to be managed according to the index data;

[0062] Among them, at least one virtual management tree at least includes a first type of node with a space location attribute and a second type of node with a logical function attribute. Different space location attributes correspond to different space locations in the specified physical space, and different logical function attributes correspond to different process links in the job processes existing in the specified physical space; the device management model is obtained by associating the nodes on at least one virtual management tree with multiple physical devices in the specified physical space.

[0063] In the embodiments of the present application, the manner of obtaining the device management model is not limited. Optionally, the device management model can be obtained by the manner in the above-mentioned device management model generation method. Based on this, as Figure 3b shown, in the embodiments of the present application, before step P1, the following steps are further included:

[0064] P01. In response to the creation operation of the space system, create a target space system, where the target space system corresponds to a specified entity space, and the specified entity space includes a plurality of entity devices;

[0065] P02. In response to the generation operation of the management model, generate at least one virtual management tree in the target space system. The at least one virtual management tree includes at least a first type of node with a spatial position attribute and a second type of node with a logical function attribute. Different spatial position attributes correspond to different spatial positions in the specified entity space, and different logical function attributes correspond to different process links in the job processes existing in the specified entity space;

[0066] P03. Combine the spatial position attributes and logical function attributes of the plurality of entity devices, and associate the plurality of entity devices with the nodes on at least one virtual management tree to obtain a multi-dimensional device management model.

[0067] It should be noted that for the specific process of the device management model generation method and the process of how to manage devices through the device management model, reference can be made to the content of the above method embodiments, and details are not repeated here. The execution subject of each step of the method provided in the above embodiments can be the same device, or the method can also be executed by different devices as the execution subject. For example, the execution subject of steps S1 to S3 and steps P1 to P3 can be device A; for another example, the execution subject of steps S1, P1, and P2 can be device A, and the execution subject of steps S2 to S3 and steps P4 can be device B; and so on.

[0068] In addition, in some processes described in the above embodiments and the accompanying drawings, a plurality of operations appear in a specific order. However, it should be clearly understood that these operations can be executed not in the order in which they appear in this article or in parallel. The operation numbers such as S1 and P1 are only used to distinguish different operations, and the numbers themselves do not represent any execution order. In addition, these processes can include more or fewer operations, and these operations can be executed in sequence or in parallel. It should be noted that the descriptions such as "first" and "second" in this article are used to distinguish different messages, devices, modules, etc., and do not represent a sequence, nor do they limit that "first" and "second" are of different types.

[0069] The embodiments of the present application further provide a device management model generation device, Figure 4The following is a schematic structural diagram of the device management model generation device provided by the embodiment of the present application. As Figure 4 shown, the device management model generation device includes a creation module 401, a first generation module 402, and a second generation module 403. Among them, the creation module 401 is used to respond to the creation operation of the space system to create a target space system, and the target space system corresponds to a specified entity space, and the specified entity space includes multiple entity devices. The first generation module 402 is used to respond to the generation operation of the management model to generate at least one virtual management tree in the target space system. At least one virtual management tree includes at least a first type of node with a spatial location attribute and a second type of node with a logical function attribute. Different spatial location attributes correspond to different spatial locations in the specified entity space, and different logical function attributes correspond to different process links in the job process existing in the specified entity space. The second generation module 403 is used to combine the spatial location attributes and logical function attributes of multiple entity devices to associate the multiple entity devices with the nodes on at least one virtual management tree to obtain a multi-dimensional device management model.

[0070] The embodiment of the present application also provides a device management device. Figure 5 The following is a schematic structural diagram of the device management device provided by the embodiment of the present application. As Figure 5 shown, the device management device includes a receiving module 501, a query module 502, and a management module 503. Among them, the receiving module 501 is used to receive a device management request, and the device management request includes a query condition, and the query condition includes at least one of a to-be-query spatial location attribute and a to-be-query logical function attribute. The query module 502 is used to traverse at least one virtual management tree in the device management model to obtain a list of device IDs that meet the query conditions, and the device management model corresponds to a specified entity space. The management module 503 is used to obtain the index data of the entity devices to be managed in the specified entity space according to the list of device IDs, so as to perform data analysis or management on the entity devices to be managed according to the index data. Among them, at least one virtual management tree includes at least a first type of node with a spatial location attribute and a second type of node with a logical function attribute. Different spatial location attributes correspond to different spatial locations in the specified entity space, and different logical function attributes correspond to different process links in the job process existing in the specified entity space. The device management model is obtained by associating the nodes on at least one virtual management tree with multiple entity devices in the specified entity space.

[0071] It should be noted that for the specific functions and implementation details of each module in the device management model generation device and the device management device provided by the embodiment of the present application, reference can be made to the description of the corresponding parts in the above method embodiment, and details are not described herein again.

[0072] The embodiment of the present application also provides an edge computing device. Figure 6The following is a schematic structural diagram of the edge computing device provided by the embodiments of the present application, as Figure 6 shown, the edge computing device includes: a processor 61, a memory 62 storing a computer program, and a display 63. Among them, the processor 61 and the memory 62 can be one or more.

[0073] The memory 62 is mainly used to store computer programs, which can be executed by the processor, causing the processor to control the processor 61 to use the edge computing device to implement corresponding functions, complete corresponding actions or tasks. In addition to storing computer programs, the memory can also be configured to store various other data to support operations on the processor 61 using the edge computing device. Examples of these data include instructions for any application program or method for operating on the processor 61 using the edge computing device.

[0074] The memory 62 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, a magnetic disk or an optical disk.

[0075] In the embodiments of the present application, the implementation form of the processor 61 is not limited. For example, it can be but is not limited to a CPU, a GPU, or an MCU, etc. The processor 61 can be regarded as the control unit of the edge computing device and can be used to execute the computer program stored in the memory 62 to control the edge computing device to implement corresponding functions, complete corresponding actions or tasks. It should be noted that according to the different implementation forms of the edge computing device and the scenarios it is in, the functions to be implemented, the actions or tasks to be completed will be different; correspondingly, the computer programs stored in the memory 62 will also be different, and the processor 61 executing different computer programs can control the edge computing device to implement different functions, complete different actions or tasks.

[0076] In some alternative embodiments, as Figure 6 shown, the edge computing device may further include: other components such as a communication component 64 and a power supply component 65. Figure 6 Only some components are schematically shown in Figure 6 which does not mean that the edge computing device only includes the

[0077] In an embodiment of the present application, when the processor 61 executes a computer program in the memory 62, it is used for: in response to a creation operation of a space system, creating a target space system, where the target space system corresponds to a specified entity space, and the specified entity space includes a plurality of entity devices; in response to a generation operation of a management model, generating at least one virtual management tree in the target space system, where the at least one virtual management tree includes at least a first type of node with a spatial position attribute and a second type of node with a logical function attribute, different spatial position attributes correspond to different spatial positions in the specified entity space, and different logical function attributes correspond to different process links in an operation process existing in the specified entity space; combining the spatial position attributes and logical function attributes of the plurality of entity devices, associating the plurality of entity devices with the nodes on the at least one virtual management tree, so as to obtain a multi-dimensional device management model.

[0078] In an alternative embodiment, when the processor 61 creates a target space system in response to a creation operation of a space system, it is used for: in response to the creation operation of the space system, displaying a space system page, and creating at least one basic tree on the space system page, where the at least one basic tree and the space system page form the target space system.

[0079] In an alternative embodiment, when the processor 61 generates at least one virtual management tree in the target space system in response to a generation operation of a management model, it is used for: in response to the generation operation of the management model, displaying the space system page corresponding to the target space system, where the space system page includes at least one basic tree, and each basic tree includes a root node and at least one level of child nodes with empty attributes; in response to an editing trigger operation on any one of the basic trees, performing an editing operation on the basic tree to obtain a virtual management tree including a root node and at least one level of child nodes with attributes, and each child node has a spatial position attribute or a logical function attribute.

[0080] In an alternative embodiment, when the processor 61 performs an editing operation on a basic tree in response to an editing trigger operation on any one of the basic trees to obtain a corresponding virtual management tree, it is used for: in response to the editing trigger operation on any one of the basic trees, displaying an editing interface, and rendering the basic tree onto the editing interface to obtain a tree to be edited, where the child nodes in the tree to be edited are bound with events corresponding to the editing operation; in response to the editing operation on the tree to be edited, obtaining the latest child nodes generated by the editing operation and their attributes and hierarchical relationships, and generating a virtual management tree according to the latest child nodes and their attributes and hierarchical relationships.

[0081] In an optional embodiment, the editing operation includes at least one of adding a child node, setting the attributes of a child node, deleting a child node, and adjusting the hierarchical relationship of child nodes. When the processor 61 obtains the latest child node and its attributes and hierarchical relationship generated by the editing operation in response to the editing operation on the tree to be edited, it is used for: in response to an attribute setting operation for any child node in the tree to be edited, displaying an attribute setting interface, and obtaining the attributes of the child node in response to an input operation on the attribute setting interface; or in response to a node adding operation for any child node in the tree to be edited, adding a next-level child node under the child node, and obtaining the attributes of the next-level child node in response to an attribute setting operation for the next-level child node; or in response to a deletion operation for any child node in the tree to be edited, deleting the child node and its attributes, and deleting the lower-level child nodes and their attributes of the child node if the child node has lower-level child nodes; or in response to a dragging operation for any child node in the tree to be edited, determining the latest parent node and / or child node of the child node according to the target position where the child node is dragged, and modifying the hierarchical relationship of the child node according to the latest parent node and / or child node.

[0082] In an optional embodiment, when there are multiple virtual management trees, the multiple virtual management trees include a first type of management tree and a second type of management tree. The first type of management tree refers to a virtual management tree in which all child nodes are first type of nodes, and the second type of management tree refers to a virtual management tree in which all child nodes are second type of nodes; when there is one virtual management tree, the virtual management tree is a third type of management tree, and the third type of management tree refers to a virtual management tree that simultaneously includes first type of nodes and second type of nodes.

[0083] In an optional embodiment, for any virtual management tree, the hierarchical relationship between child nodes reflects the hierarchical relationship or cascading relationship between the attributes of each layer of child nodes, and each layer of child nodes has one or both of a spatial position attribute and a logical function attribute, and there is one or more of the same type of attribute.

[0084] In an optional embodiment, when the processor 61 combines the spatial position attributes and logical function attributes of multiple entity devices and associates the multiple entity devices with the nodes on at least one virtual management tree to obtain a multi-dimensional device management model, it is used for: for each child node on each virtual management tree, in response to an association trigger operation for the child node, displaying the attributes of the child node and a device association interface; and in response to an input operation on the device association interface, obtaining the identifier of the target entity device to be associated with the child node, and adding the identifier of the target entity device to the device asset list of the child node, where the target entity device has attributes adapted to the child node.

[0085] In an alternative embodiment, when adding the identifier of the target entity device to the device asset list of the child node, the processor 61 is configured to: determine whether the target entity device has an attribute adapted to the child node according to the identifier of the target entity device; in the case of not having it, output a prompt message for the relevant personnel to confirm whether to establish an association relationship between the child node and the target entity device; and in the case of receiving a confirmation association instruction, add the identifier of the target entity device to the device asset list of the child node.

[0086] In an alternative embodiment, after obtaining the device management model, the processor 61 is further configured to: receive a device management request, where the device management request includes a query condition, and the query condition includes at least one of a to-be-query spatial location attribute and a to-be-query logical function attribute; traverse at least one virtual management tree in the device management model to obtain a list of device IDs that meet the query condition; and obtain the metric data of the to-be-managed entity device in the specified entity space according to the list of device IDs, and perform data analysis or management on the to-be-managed entity device according to the metric data.

[0087] Correspondingly, an embodiment of the present application further provides a computer-readable storage medium storing a computer program, which when executed by a processor causes the processor to implement the steps in the above method embodiments.

[0088] Correspondingly, an embodiment of the present application further provides a computer program product, including a computer program / instructions, which when executed by a processor causes the processor to implement the steps in the above method embodiments.

[0089] The communication component in the above embodiments is configured to facilitate communication between the device where the communication component is located and other devices in a wired or wireless manner. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G / LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component further includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on technologies such as Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0090] The display in the above embodiments includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can sense not only the boundaries of touch or swipe actions, but also detect the duration and pressure associated with the touch or swipe operation.

[0091] The power supply component in the above embodiments provides power for various components of the device where the power supply component is located. The power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device where the power supply component is located.

[0092] The audio component in the above embodiments can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC), which is configured to receive external audio signals when the device where the audio component is located is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals can be further stored in a memory or sent via a communication component. In some embodiments, the audio component further includes a speaker for outputting audio signals.

[0093] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program code.

[0094] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0095] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce a manufacture including an instruction device that implements the functions specified in one or more of the flows Figure 1 one or more of the flows and / or blocks Figure 1 specified in one or more of the blocks or blocks.

[0096] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus so that a series of operational steps are performed on the computer or other programmable apparatus to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable apparatus provide steps for implementing the functions specified in one or more of the flows Figure 1 one or more of the flows and / or blocks Figure 1 specified in one or more of the blocks or blocks.

[0097] It should also be noted that the terms "comprising", "including" or any other variation thereof are intended to cover non-exclusive inclusion, such that a process, method, article or apparatus comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or apparatus. Without further limitation, an element defined by the statement "comprising a..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising the element.

[0098] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, various changes and modifications can be made to the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included within the scope of the claims of the present application.

Claims

1. A method for generating a device management model, characterized in that Including: In response to the creation operation of the space system, a target space system is created. The target space system corresponds to a specified entity space, and the specified entity space includes multiple entity devices. The target space system, as a logical management space, is used to carry the space positions in the specified entity space that are adapted to the user management requirements, the job processes in the specified entity space that are adapted to the user management requirements, and the process links in the job processes. In response to the generation operation of the management model, at least one virtual management tree is generated in the target space system. The at least one virtual management tree includes at least a first type of node with a space position attribute and a second type of node with a logical function attribute. Different space position attributes correspond to different space positions in the specified entity space, and different logical function attributes correspond to different process links in the job processes existing in the specified entity space. Combining the space position attributes and logical function attributes of the multiple entity devices, the multiple entity devices are associated with the nodes on the at least one virtual management tree to obtain a multi-dimensional device management model.

2. The method according to claim 1, characterized in that, In response to the creation operation of the space system, a target space system is created, including: In response to the creation operation of the space system, a space system page is displayed, and at least one basic tree is created on the space system page. The at least one basic tree and the space system page form a target space system.

3. The method according to claim 2, wherein In response to the generation operation of the management model, at least one virtual management tree is generated in the target space system, including: In response to the generation operation of the management model, the space system page corresponding to the target space system is displayed. The space system page includes at least one basic tree, and each basic tree includes a root node and at least one level of child nodes with empty attributes. In response to the editing trigger operation on any one of the basic trees, an editing operation is performed on the basic tree to obtain a virtual management tree including a root node and at least one level of child nodes with attributes. Each child node has a space position attribute or a logical function attribute.

4. The method according to claim 3, characterized in that, In response to the editing trigger operation on any one of the basic trees, an editing operation is performed on the basic tree to obtain a corresponding virtual management tree, including: In response to the editing trigger operation on any one of the basic trees, an editing interface is displayed, and the basic tree is rendered onto the editing interface to obtain a tree to be edited. The child nodes in the tree to be edited are bound with events corresponding to the editing operation. In response to the editing operation on the tree to be edited, the latest child nodes generated by the editing operation, their attributes, and their hierarchical relationships are obtained, and a virtual management tree is generated according to the latest child nodes, their attributes, and their hierarchical relationships.

5. The method according to claim 4, wherein The editing operation includes at least one of adding child nodes, setting child node attributes, deleting child nodes, and adjusting child node hierarchical relationships. Then, in response to the editing operation on the tree to be edited, obtaining the latest child nodes generated by the editing operation, their attributes, and their hierarchical relationships includes: In response to the attribute setting operation on any one of the child nodes in the tree to be edited, an attribute setting interface is displayed, and in response to the input operation on the attribute setting interface, the attributes of the child node are obtained. Or In response to a node addition operation for any sub - node in the tree to be edited, add a next - level sub - node under the sub - node, and in response to an attribute setting operation for the next - level sub - node, obtain the attributes of the next - level sub - node; Or In response to a deletion operation for any sub - node in the tree to be edited, delete the sub - node and its attributes, and in the case where the sub - node has lower - level sub - nodes, delete the lower - level sub - nodes and their attributes of the sub - node; or In response to a drag - and - drop operation for any sub - node in the tree to be edited, determine the latest parent node and / or sub - node of the sub - node according to the target position where the sub - node is dragged, and modify the hierarchical relationship of the sub - node according to the latest parent node and / or sub - node.

6. The method according to any one of claims 3 to 5, characterized in that, In the case where there are multiple virtual management trees, the multiple virtual management trees include a first - type management tree and a second - type management tree. The first - type management tree refers to a virtual management tree in which all sub - nodes are first - type nodes, and the second - type management tree refers to a virtual management tree in which all sub - nodes are second - type nodes; In the case where there is one virtual management tree, the virtual management tree is a third - type management tree. The third - type management tree refers to a virtual management tree that simultaneously includes first - type nodes and second - type nodes.

7. The method according to claim 6, wherein For any virtual management tree, the hierarchical relationship between sub - nodes reflects the hierarchical relationship or cascading relationship between the attributes of each layer of sub - nodes, and each layer of sub - nodes has one or both of a spatial position attribute and a logical function attribute, and each type of attribute has one or more.

8. The method according to any one of claims 1-5, characterized in that, Combining the spatial position attributes and logical function attributes of the multiple physical devices, associate the multiple physical devices with the nodes on at least one virtual management tree to obtain a multi - dimensional device management model, including: For each sub - node on each virtual management tree, in response to an association trigger operation for the sub - node, display the attributes of the sub - node and a device association interface; In response to an input operation on the device association interface, obtain the identifier of the target physical device to be associated with the sub - node, and add the identifier of the target physical device to the device asset list of the sub - node. The target physical device has attributes adapted to the sub - node.

9. The method according to claim 8, characterized in that Adding the identifier of the target physical device to the device asset list of the sub - node includes: Judging whether the target physical device has attributes adapted to the sub - node according to the identifier of the target physical device; In the case of not having, output a prompt message for the relevant person to confirm whether to establish an association relationship between the sub - node and the target physical device; In the case of receiving a confirmation association instruction, add the identifier of the target physical device to the device asset list of the sub - node.

10. The method according to any one of claims 1-5, characterized in that, After obtaining the device management model, it further includes: Receiving a device management request, the device management request includes a query condition, and the query condition includes at least one of a spatial position attribute to be queried and a logical function attribute to be queried; Traverse at least one virtual management tree in the device management model to obtain a list of device IDs that meet the query condition; Obtain the metric data of the entity devices to be managed in the specified entity space according to the device ID list, and perform data analysis or management on the entity devices to be managed according to the metric data.

11. A device management method, characterized in that, Including: Receive a device management request, where the device management request includes a query condition, and the query condition includes at least one of a space location attribute to be queried and a logical function attribute to be queried; Traverse at least one virtual management tree in the device management model to obtain a device ID list that meets the query condition, where the device management model corresponds to the specified entity space; Obtain the metric data of the entity devices to be managed in the specified entity space according to the device ID list, and perform data analysis or management on the entity devices to be managed according to the metric data; Wherein, the at least one virtual management tree at least includes a first type of node with a space location attribute and a second type of node with a logical function attribute, different space location attributes correspond to different space locations in the specified entity space, and different logical function attributes correspond to different process links in the job processes existing in the specified entity space; The device management model is obtained by associating the nodes on the at least one virtual management tree with multiple entity devices in the specified entity space, and the device management model is generated according to the method described in Claim 1.

12. An apparatus for generating a device management model, characterized in that, Including: A creation module, configured to respond to a creation operation of a space system to create a target space system, where the target space system corresponds to the specified entity space, and the specified entity space includes multiple entity devices; the target space system, as a logical management space, is used to carry the space locations in the specified entity space that match the user management requirements, the job processes in the specified entity space that match the user management requirements, and the process links in the job processes; A first generation module, configured to respond to a generation operation of a management model to generate at least one virtual management tree in the target space system, where the at least one virtual management tree at least includes a first type of node with a space location attribute and a second type of node with a logical function attribute, different space location attributes correspond to different space locations in the specified entity space, and different logical function attributes correspond to different process links in the job processes existing in the specified entity space; A second generation module, configured to combine the space location attributes and logical function attributes of the multiple entity devices to associate the multiple entity devices with the nodes on the at least one virtual management tree to obtain a multi-dimensional device management model.

13. An edge computing device, characterized in that, Including: A display, a processor, and a memory storing a computer program, where the processor is configured to execute the computer program to execute the steps in the method described in any one of Claims 1-11.

14. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it causes the processor to implement the steps in the method described in any one of Claims 1-11.

Images