WO2023179504A1 - 设备管理模型生成与设备管理方法、设备及存储介质 - Google Patents

设备管理模型生成与设备管理方法、设备及存储介质 Download PDF

Info

Publication number
WO2023179504A1
WO2023179504A1 PCT/CN2023/082342 CN2023082342W WO2023179504A1 WO 2023179504 A1 WO2023179504 A1 WO 2023179504A1 CN 2023082342 W CN2023082342 W CN 2023082342W WO 2023179504 A1 WO2023179504 A1 WO 2023179504A1
Authority
WO
WIPO (PCT)
Prior art keywords
tree
node
attributes
nodes
management
Prior art date
Application number
PCT/CN2023/082342
Other languages
English (en)
French (fr)
Inventor
钟汉津
郑银辉
赵熙朝
蔡热文
杜稼淳
陈斯林
Original Assignee
阿里云计算有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里云计算有限公司 filed Critical 阿里云计算有限公司
Publication of WO2023179504A1 publication Critical patent/WO2023179504A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06315—Needs-based resource requirements planning or analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0633—Workflow analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/04—Manufacturing
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Definitions

  • This application relates to the field of edge cloud technology, and in particular to a device management model generation and device management method, device and storage medium.
  • Various aspects of this application provide a device management model generation and device management method, device, and storage medium to manage physical devices in the physical space from multiple dimensions of spatial location and logical functions.
  • Embodiments of the present application provide a device management model generation method, including: in response to a creation operation of a space system, creating a target space system, the target space system corresponding to a designated entity space, and the designated entity space includes multiple entity devices; 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 at least includes 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 designated entity space
  • different logical function attributes correspond to different process links in the operation process existing in the designated entity space
  • Attributes and logical function attributes are used to associate the plurality of physical devices with nodes on the at least one virtual management tree to obtain a multi-dimensional device management model.
  • An embodiment of the present application also provides a device management method, including: receiving a device management request, the device management The processing request includes query conditions, and the query conditions include at least one of spatial location attributes to be queried and logical function attributes to be queried; at least one virtual management tree in the device management model is traversed to obtain devices that meet the query conditions.
  • the device management model corresponds to the designated entity space; obtain the indicator data of the entity device to be managed in the designated entity space according to the device ID list, perform data analysis on the entity device to be managed according to the indicator data, or Management; wherein the at least one virtual management tree includes at least a first type of node with spatial location attributes and a second type of node with logical function attributes, and different spatial location attributes correspond to different spatial locations in the designated entity space, Different logical function attributes correspond to different process links in the operation process existing in the designated physical space; the device management model is a node on the at least one virtual management tree and multiple physical devices in the designated physical space. Obtained by association.
  • Embodiments of the present application also provide an equipment management model generation device, including: a creation module, configured to create a target space system in response to a creation operation of a space system, where the target space system corresponds to a designated entity space, and the designated entity
  • the space includes a plurality of physical devices;
  • the first generation module is configured to generate at least one virtual management tree in the target space system in response to the generation operation of the management model, and the at least one virtual management tree at least includes a spatial location
  • the first type of nodes with attributes and the second type of nodes with logical function attributes Different spatial location attributes correspond to different spatial locations in the specified entity space, and different logical function attributes correspond to the job processes existing in the specified entity space. Different process links;
  • the second generation module is used to associate the multiple physical devices with the nodes on the at least one virtual management tree by combining the spatial location attributes and logical function attributes of the multiple physical devices, so as to Get a multi-dimensional device management model.
  • An embodiment of the present application also provides an equipment management device, including: a receiving module, configured to receive a equipment management request, where the equipment management request includes query conditions, and the query conditions include spatial location attributes to be queried and logical function attributes to be queried. At least one of; a query module, 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 the specified entity space; a management module, used to Obtain the indicator data of the entity device to be managed in the designated entity space according to the device ID list, so as to perform data analysis or management on the entity device to be managed according to the indicator data; wherein, the at least one virtual management tree It includes at least a first type of node with spatial location attributes and a second type of node with logical function attributes.
  • Different spatial location attributes correspond to different spatial locations in the specified entity space, and different logical function attributes correspond to existence in the specified entity space.
  • Different process links in the operation process; the device management model is obtained by associating nodes on the at least one virtual management tree with multiple physical devices in the designated physical space.
  • An embodiment of the present application also provides an edge computing device, including: a display, a processor, and a memory storing a computer program.
  • the processor is configured to execute the computer program to execute any of the methods. One step.
  • Embodiments of the present application also provide a computer-readable storage medium storing a computer program.
  • the computer program When executed by a processor, it causes the processor to implement any one of the steps.
  • Embodiments of the present application also provide a computer program product, which includes a computer program/instruction.
  • a computer program/instruction When executed by a processor, it causes the processor to implement any step in the method.
  • the user can create a target space system corresponding to the specified physical space to create a virtual management tree corresponding to the specified physical space in the target space system; further, through the location space attributes on the virtual management tree
  • the nodes with logical function attributes are associated with the physical devices in the physical space, so that the nodes on the virtual management tree can point to different spatial locations in the physical space and to different process links in the physical space, and generate data that can be generated from the spatial locations and logical functions.
  • a device management model that manages physical devices from different dimensions.
  • users can obtain the device management model generated above, and use the obtained device management model to manage physical device entities in the physical space from multiple dimensions of spatial location and logical functions, with more diverse management methods.
  • Figure 1 is a flow chart of a device management model generation method provided by an embodiment of the present application.
  • Figure 2a is a schematic diagram of a service page for creating a target space system provided by an embodiment of the present application
  • Figure 2b is a schematic diagram of a spatial system page for displaying a basic tree provided by an embodiment of the present application
  • Figure 2c is a schematic diagram of an editing interface for editing a basic tree provided by an embodiment of the present application.
  • Figure 2d is a schematic diagram after editing the basic tree provided by the embodiment of the present application.
  • Figure 2e is a schematic diagram of an operation interface of a derivation space system provided by an embodiment of the present application.
  • Figure 3a is a flow chart of a device management method provided by an embodiment of the present application.
  • Figure 3b is a flow chart of another device management model generation method provided by an embodiment of the present application.
  • Figure 4 is a schematic structural diagram of a device management model generation device provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of an equipment management device provided by an embodiment of the present application.
  • Figure 6 is a schematic structural diagram of an edge computing device provided by an embodiment of the present application.
  • the physical world mapping method is usually used 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 mapping.
  • the production equipment in each workshop is managed and maintained.
  • production structures such as factories, workshops, workstations, production lines/processes, and production equipment used in each process on the production line/process are usually involved.
  • the equipment management model supports the management of physical equipment in various industries from multiple dimensions, and can not only manage the physical equipment from the spatial location dimension of different granularities, Management can also manage physical devices from the logical functional dimensions of different granularities.
  • the equipment management model provided by the embodiments of this application can be applied to various industries involving physical equipment that need to be managed, such as various production industries, logistics industries, warehousing management industries, etc.
  • the physical devices in the various embodiments of this application refer to physical devices that need to be managed in various industries. These physical devices will also vary depending on the application industry. Taking the production industry as an example, these physical equipment can be various production equipment.
  • these physical equipment involve production equipment such as cloth cutting machines, ironing machines, printing and dyeing machines, and sewing machines.
  • these physical equipment involve various logistics equipment such as sealing equipment, labeling equipment, loading and unloading equipment, handling robots, and cargo transportation equipment.
  • embodiments of the present application can provide an edge computing device, which is responsible for generating the new device management model and based on This device management model performs device management.
  • the edge computing device provided by the embodiment of this application is a computing device that can be deployed at the edge of a cloud network and has computing, network, storage, security and other capabilities.
  • the edge computing device can be implemented as one or more servers and software programs deployed on the servers. These servers and software programs can be packaged together as a cloud product in the form of edge deployment (i.e., edge computing device ) is provided to enterprise users.
  • enterprise users can be provided with device management model generation services and device management services based on the generated device management models.
  • Enterprise users can deploy edge computing devices into the enterprise's on-site environment, or in the computer room or Internet Data Center (IDC) in the edge cloud system close to the enterprise's on-site environment. There is no limit to this.
  • enterprise users can use the device management model generation service provided by the edge computing device to generate a device management model adapted to their application requirements, and based on the device management model, they can generate spatial locations and logical functions of different granularities based on the device management model. Multi-dimensional management of various physical devices within the enterprise.
  • the generation process of the device management model and the device management process based on the device management model will be described in detail.
  • Embodiments of the present application provide a device management model generation method, through which a device management model capable of managing physical devices from multiple dimensions can be generated for use by developers or front-line operators in various industries, and for related physical devices. ready for management.
  • Figure 1 is a flow chart of a device management model generation method provided by an embodiment of the present application. As shown in Figure 1, the method includes:
  • the target space system corresponds to the designated entity space, and the designated entity space includes multiple entity devices;
  • the at least one virtual management tree at least includes first-type nodes with spatial location attributes and second-type nodes with logical function attributes. , 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 space system is a logical management space that can be defined by users according to their own management needs. Assuming that the user has management requirements for the physical equipment in the specified physical space, a corresponding space system can be established for the specified physical space. As a logical management space, the space system can host the adaptation of the user management needs in the specified physical space.
  • these spatial locations and process links that are adapted to user management needs can also be called spatial resources or resource objects in the spatial system.
  • spatial resources or resource objects can also be called spatial resources or resource objects in the spatial system.
  • the unique identifier of the space system can be called a system code (SystemCode), users can query the corresponding space system through the system code.
  • a service page can be displayed, which includes functional controls for creating a space system for users to use when needed. can initiate the operation of creating a space system.
  • users When users have management requirements for physical equipment in a specified physical space, they can initiate a space system creation operation through this functional control.
  • a space system corresponding to the specified entity space can be created, and the created space system can be rendered to the area below the function control.
  • the space system corresponding to the specified entity space is called the target space system.
  • the specific type of the designated physical space is not limited.
  • the designated physical space can be a factory, a workshop, or multiple workshops or multiple factories; for example, in the warehousing and logistics industry, the designated physical space can be a warehouse, and so on.
  • the designated physical space can be a factory, a workshop, or multiple workshops or multiple factories; for example, in the warehousing and logistics industry, the designated physical space can be a warehouse, and so on.
  • At least one virtual management tree can be generated in the target space system, and the physical devices in the designated physical space are managed through nodes on these virtual management trees.
  • Each virtual management tree has a unique identifier.
  • the unique identifier of the virtual management tree can be called a space code (spaceCode).
  • spaceCode space code
  • the user can query the corresponding virtual management tree through the space code.
  • at least one virtual management tree may be generated in the target space system.
  • 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 third type of nodes with logical function attributes.
  • spatial location attributes and logical function attributes are two major categories of attributes. Each attribute can also have attributes with different granularities. That is to say, from the perspective of attribute granularity, the spatial location attributes have multiple, logical There can also be multiple functional attributes; further, at the same granularity, there can be multiple spatial location attributes, and there can also be multiple logical functional attributes.
  • the factory is a granularity
  • the workshop is a granularity.
  • the production line is A granularity, a process is a granularity.
  • n, m, k, and p are all natural numbers greater than or equal to 2. It should be noted that these attribute granularities and attribute divisions at the same granularity are divided according to the management needs of users, and may be the same as the granularity and quantity of location spaces and the granularity and quantity of production lines and processes that exist in actual production. Can be different.
  • the number of first-type nodes is one or more, and in the case of multiple nodes, the spatial location attributes corresponding to different first-type nodes may be the same or different; similarly, the second-type nodes may have the same spatial location attributes.
  • the number of 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.
  • different spatial position attributes correspond to different spatial positions in the specified entity space. That is to say, the first type of nodes corresponding to different spatial position attributes point to different spatial positions in the entity space.
  • two nodes with different spatial location 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.
  • different logical function attributes correspond to different process links in the job process existing in the specified entity space. That is to say, the second type of nodes corresponding to different logical function attributes point to different process links. For example, for two nodes with different logical functional attributes, one node represents process 1 and the other may represent process 2, or one node represents production line 1 and the other node may represent process 2.
  • the embodiment of the present application does not limit the number of virtual management trees included in the target space system. It may be one or multiple trees.
  • the virtual management tree includes two types of nodes at the same time, that is, it includes both the first type of nodes and the second type of nodes, which has both spatial location attributes and logical functions. Mixed tree of attributes.
  • the target space system contains two or more virtual management trees, there are the following two situations:
  • Case 1 These virtual management trees include the first type of management tree and the second type of management tree; among them, the nodes on the first type of management tree are all first type nodes, and the nodes on the second type of management tree are all of the second type. node.
  • Case 2 These virtual management trees are all third-category management trees, that is, there are first-category nodes and second-category nodes on the third-category management tree.
  • 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 at the same time.
  • each physical device has both spatial location attributes and logical function attributes. These spatial location attributes and logical function attributes are also granular, and there are multiple different attributes at the same granularity.
  • the equipment management requirement is to manage the equipment on the first spatial location attribute, then the entity device with the first spatial location attribute can be associated with the node with the first spatial location attribute; in another case, in one case, the device management requirement is to manage the physical device with the first logical function attribute on the first spatial location attribute, then the physical device with the first logical function attribute on the first spatial location attribute can be combined with the first physical device with the first logical function attribute on the first spatial location attribute.
  • the nodes with logical function attributes are associated.
  • the equipment management requirement is to manage equipment A in workshop 1, then the node with the spatial location attribute of workshop 1 can be associated with equipment A; in another case, equipment management The requirement is to manage the entity device with the first logical function attribute on the first spatial location attribute, then the entity device with the first logical function attribute on the first spatial location attribute can be associated with the node with the first logical function attribute.
  • the equipment management requirement is to manage equipment B responsible for the printing process in workshop 2
  • the node whose logical function attribute is the printing process can be associated with equipment B, and so on.
  • the user can create a target space system corresponding to the specified physical space through the edge device, so as to create a virtual system corresponding to the specified physical space in the target space system.
  • Management tree further, by associating the nodes with location space attributes and logical function attributes on the virtual management tree with the physical devices in the physical space, the nodes on the virtual management tree can point to different spatial locations in the physical space and to entities. Different process links in the space can be generated from A device management model that manages physical devices from different dimensions of spatial location and logical functions.
  • edge devices also provide device management services. Based on this device management service, users can obtain the device management model generated above, and use the obtained device management model to manage physical devices in the physical space from multiple dimensions of spatial location and logical functions. Entities are managed, and the management methods are richer and more diverse.
  • the specific method of creating the target space system is not limited.
  • the space system page in response to the user performing a trigger operation on the "Create Space System" function control on the service page, as shown in Figure 2b,
  • the space system page can be displayed, and at least one basic tree can be created on the space system page; wherein the at least one basic tree and the space system page form the target space system of this embodiment.
  • the target space system of this embodiment is a page with management functions, and there is at least one basic tree on the page.
  • each basic tree may include a root node and at least one level of child nodes with empty attributes.
  • At least one basic tree can have exactly the same structure, that is, have the same node level and include the same number of nodes on each layer, or Can have different structures; among them, the nodes on each base tree have corresponding attributes, but in the initial stage, the attributes of each node are empty.
  • the number of basic trees is not limited. In different spatial systems, the number of basic trees may be the same or different.
  • users are allowed to delete or add these basic trees. Specifically, as shown in Figure 2b, in the space system page, the area where the basic tree is located contains the "Add" control and the "Delete" control.
  • the user triggers the "Add" control to continue to add a new basic tree in the area where the basic tree is located. And when the basic tree of any lesson is selected, triggering the "Delete” control can delete the selected basic tree.
  • the basic tree setting page can also be displayed. The user can set the structural information of the basic tree through the basic tree setting page, that is, the user can set the number of layers of the basic tree and the content contained in each layer. The number of nodes and the parent-child relationship between nodes, etc., are then used to generate a new basic tree based on the structural information of the basic tree set by the user and present it on the spatial system page.
  • these basic trees are the basis for generating a virtual management tree, and these basic trees are allowed to be edited in order to generate a corresponding virtual management tree.
  • the user can edit the basic tree in the target space system to generate a virtual management tree based on the basic tree.
  • 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.
  • 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 the editing control.
  • the triggering method can be but not limited to any of the following: click, double-click, long press, touch, mouse hover. Stop and wait. Based on this, it can respond to the editing trigger operation initiated by the user on any basic tree, and then respond to the editing trigger operation on any basic tree.
  • the editing interface corresponding to the basic tree to be edited can be displayed, and the basic tree is rendered to the editing interface to obtain the tree to be edited; wherein, the process of rendering the basic tree to the editing interface includes : Render a canvas on the display screen.
  • the canvas provides basic interactive tools such as full screen and zoom.
  • the canvas also includes an editing area.
  • the canvas can be used according to the structure of the basic tree, that is, the root
  • the parent-child relationship (or hierarchical relationship) between a node and its sub-nodes at all levels starts from the root node recursively and renders each node in the editing area according to the hierarchy; in this process, in order to facilitate the user to understand the basics
  • each node can be bound to the editing events corresponding to the preset editing operations, such as click events, drag events, etc.
  • the nodes after binding the editing events support users to correspond to them. Editing operations, for example, the user can click or drag the node, etc.
  • nodes other than the root node are called child nodes.
  • the basic tree on the editing interface is in an editable state, so it is called the tree to be edited.
  • the user can obtain a virtual management tree after performing various editing operations on the tree to be edited.
  • the user can trigger any sub-node to edit it.
  • the events bound to the sub-node include but are not limited to attribute setting events, node addition events, node deletion events, drag and drop events, etc.
  • These editing events correspond to different editing operations.
  • different types of editing operations can be performed on the child node. For example, for any child node, you can trigger the attribute setting event through the attribute editing operation to edit the attributes of the child node. You can also trigger the node adding event through the node adding operation to add subordinate child nodes to the child node.
  • the deletion operation triggers the node deletion event, thereby deleting the child node.
  • These editing operations or events will generate the latest child nodes and their attributes and hierarchical relationships. Based on this, in response to the user's editing operation on the edit tree, the latest child nodes generated by the editing operation and their properties and hierarchical relationships can be obtained. , and generate a virtual management tree based on the latest child nodes and their attributes and hierarchical relationships.
  • the types of editing operations that the user can perform on each sub-node in the editing tree and the specific manner of performing the editing operations are not limited.
  • the editing operation can be at least one of adding sub-nodes, setting sub-node attributes, deleting sub-nodes, and adjusting sub-node hierarchical relationships; further optionally, the user performs any of the above operations on the sub-nodes in the tree to be edited.
  • the corresponding event can be triggered by triggering any sub-node, so that when the corresponding type of event is responded to, the corresponding type of editing operation can be performed.
  • the attribute setting event corresponding to the sub-node in response to the user's attribute setting operation for any sub-node in the tree to be edited, can be triggered to display the attribute setting interface; further, the user can enter the sub-node in the attribute setting interface.
  • the attribute information corresponding to the node can be obtained in response to the user's input operation on the attribute setting interface.
  • the node addition event corresponding to the child node in response to the user's node addition operation for any sub-node in the tree to be edited, The node addition event corresponding to the child node can be triggered to add the next level child node below the child node.
  • Figure 2d is a schematic diagram after adding next-level sub-nodes under the two sub-nodes of the basic tree.
  • the next-level sub-nodes of the root node of the basic tree are sub-node 1, sub-node 2 and sub-node 3 respectively.
  • the user adds next-level sub-node 11, sub-node 12 and sub-node 13 respectively under sub-node 1, and adds next-level sub-node 31 and sub-node 32 under sub-node 3.
  • the user can also perform an attribute setting operation on the newly added next-level child node to set its attributes; based on this, in response to the user's attribute setting operation on the next-level child node, the next step can be triggered.
  • the attribute setting event corresponding to the first-level sub-node is displayed to display the attribute setting interface; further, the user can input the attribute information corresponding to the next-level sub-node in the attribute setting interface, and then in response to the user's input operation on the attribute setting interface In the case of , you can get the attributes corresponding to the next-level child nodes.
  • the node deletion event corresponding to the sub-node in response to the user's deletion operation on any sub-node in the tree to be edited, the node deletion event corresponding to the sub-node can be triggered to delete the sub-node and its attributes, and when the sub-node has subordinate sub-nodes In this case, delete the child node's subordinate child nodes and their attributes.
  • the drag event corresponding to the sub-node can be triggered; further, according to the target position to which the sub-node is dragged, the sub-node can be determined.
  • the latest parent node and/or child node of the node and modify the hierarchical relationship of the child node based on the latest parent node and/or child node.
  • a function list can be displayed in the form of a pop-up window or a floating layer, and the list can include "attributes”.
  • Function tags such as “Settings”, “Node Added”, “Node Deleted” or “Node Adjustment”, users can trigger any tag to initiate the corresponding editing operation.
  • the attribute setting interface can be displayed for the user to input the attribute information of the node; when the user triggers the "Node Add” label, the next level child node can be added to the current child node; when the user When the "Node Delete” label is triggered, the current child node and its attributes can be deleted, or the subordinate child nodes and their attributes connected to the current child node can be deleted together; when the user triggers the "Node Adjustment” label, the current child node becomes available for deletion.
  • the user can drag the current node to any child node or the next level of the root node as its child node, and modify the hierarchical relationship of the child nodes according to the latest parent node and/or child node, etc.
  • the above editing methods are only exemplary descriptions and are not limited thereto.
  • the user can directly trigger any child node to initiate the corresponding editing operation.
  • the next-level sub-node can be automatically added to it; in response to the user double-clicking on any sub-node, the sub-node can be deleted directly, or together with the current The lower-level child nodes and their attributes of the child node are deleted together; the child node can be dragged by default, and the user can directly drag the current child node to any child node or the next level of the root node as its child node, and according to the latest The parent node and/or child node of the child node modify the hierarchical relationship of the child node, etc.; for another example, when any child node is selected, you can also use the shortcut key Add next-level sub-nodes to the selected sub-node or delete the selected sub-node, etc.; of course, you can also edit the to-be-edited tree through any two or more combinations of the above to generate the corresponding virtual management tree, specifically It can be determined according to actual needs
  • the attributes of each sub-node on the same level of a tree to be edited can be the spatial location attribute of a certain granularity, or the logical function attribute of a certain granularity, or some of the sub-nodes can be the attributes of a certain granularity.
  • the spatial location attributes of It depends on management needs and is not limited. For example, assuming that the first layer has two child nodes, set the spatial location attribute for a child node on the first layer, and its spatial location attribute is specifically workshop 1, and set the spatial location attribute for another child node on the first layer.
  • the logical function attribute can be set for the second-level sub-node, assuming that the logical function attribute is set for the next-level sub-node of the sub-node Workshop 1, and its logical function attribute is specific
  • process 1 corresponding to production line 1 set the logical function attribute for the next-level child node of workshop 2
  • its logical function attribute is specifically process 2 corresponding to production line 2.
  • the first layer has two child nodes. Set a child node on the first layer to have a spatial location attribute, and its spatial location attribute is specifically workshop 1. Set another child node on the first layer to have a logical location.
  • Functional attributes, and its logical functional attributes are specifically process 1 corresponding to production line 1; further, logical functional attributes can be set for the next-level sub-node of the sub-node workshop 1, and its logical functional attributes are specifically corresponding to production line 2.
  • set the spatial location attribute for the next-level sub-node of the sub-node of process 1, and its spatial location attribute is specifically workshop 2, and so on.
  • the generated virtual management tree is not mapped according to the actual location of the specified entity space in the physical world, but is mapped according to the enterprise's factory, workshop, production line/process, and production line/process.
  • the spatial location and logical functions corresponding to the physical equipment used in the process are obtained. Therefore, at least one virtual management tree in the target space system includes at least two types of nodes, that is, two types of nodes with spatial location attributes or logical function attributes.
  • the virtual management trees can be classified according to the types of nodes. In this embodiment of the present application, when classifying the virtual management tree, child nodes are mainly considered and the root node is not considered.
  • a virtual management tree in which all sub-nodes have spatial location attributes is called a first-type management tree
  • a virtual management tree in which all sub-nodes have logical function attributes is called a second-type management tree
  • some sub-nodes are A virtual management tree with spatial location attributes and some sub-nodes with logical function attributes is called the third type of management tree.
  • the embodiments of the present application do not limit the number of virtual management trees and the type of virtual management trees.
  • the multiple virtual management trees may include first-type management trees and The second type management tree or multiple virtual management trees are all third type management trees; in the case of one virtual management tree, the virtual management tree is the third type management tree.
  • the hierarchical relationship between sub-nodes reflects the hierarchical relationship or cascade relationship between the attributes of sub-nodes at each level.
  • Sub-nodes at the same level have one or both types of spatial location attributes and logical function attributes.
  • the same type of attributes can have one or more types.
  • the specific structure of each virtual management tree can be determined based on the enterprise's factory, workshop, production line/process, and the corresponding spatial location and logical functions of the physical equipment used in each process on the production line/process. In this way, the generated virtual management tree can be used as an equipment management model for enterprise management of factories, workshops, production lines/processes, and physical equipment, so that the usage status of physical equipment can be easily and intuitively understood from the perspective of production lines/processes.
  • the number of spatial location attributes and logical function attributes corresponding to the child nodes in each virtual management tree is not limited.
  • the number of spatial location attributes and logical function attributes can be one or more.
  • each space location attribute corresponds to a spatial location in the specified entity space, and different spatial location attributes correspond to different spatial locations; of course, the first type of nodes with the same spatial location attribute should correspond to the specified For the same spatial position in the entity space, first-type nodes with different spatial position attributes correspond to different spatial positions in the specified entity space.
  • the sub-node 1 and sub-node 2 associated with equipment 1 and equipment 2 respectively are both first-type nodes and correspond to the same spatial location as workshop A; for another example, equipment 3 is located in workshop B, and equipment 4 is located in workshop C. Then the sub-node 3 and sub-node 4 associated with equipment 3 and equipment 4 respectively are both first-type nodes, but correspond to different spatial positions, namely workshop B and workshop C respectively. .
  • each logical function attribute corresponds to a process link in the job process in the specified entity space
  • different logical function attributes correspond to different process nodes in the job process in the specified entity space
  • the second type of nodes with the same logical function attributes correspond to the same process link in the job process in the specified entity space
  • the second type of nodes with different logical function attributes correspond to different process links in the job process in the specified entity space.
  • equipment 1 and equipment 2 are both equipment responsible for the printing process in the printing production line, then the child nodes 1 and 2 associated with equipment 1 and equipment 2 respectively are second-type nodes with printing logic functional attributes, and correspond to The same process node is the printing process; for another example, equipment 3 is the equipment responsible for the copying process in the printing production line, and equipment 4 is the equipment responsible for the cutting process in the printing production line, then the child node 3 associated with equipment 3 has the copying process.
  • the second type of node with logical function attributes, the corresponding process link is the copying process, and the child node 4 associated with the device 4 is the second type of node with the logical function attribute of raw cutting, and the corresponding process link is the raw cutting process.
  • the segmentation granularity of the process links in the embodiment of this application is determined according to the equipment management requirements, and may be the same as or different from the process joints in the actual operation process, and is not limited here.
  • each sub-node in the virtual management tree can also be bound to a device association event, so that users can associate the sub-nodes in the virtual management tree with physical devices; further optionally, the sub-nodes in the virtual management tree can be The sub-node also corresponds to a device asset list, which contains the identifier of the physical device associated with the sub-node. For each sub-node, when the user associates it with an physical device, the identifier of the associated physical device will be Added to the device asset list corresponding to the current child node.
  • each child node on each virtual management tree can be Execute the association trigger operation to trigger the device association event corresponding to the child node; based on this, when responding 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 identification of the target entity device.
  • the identity of the target entity device that needs to be associated with the child node can be obtained, and the identity of the target entity device is added to the device asset list of the child node; where, the target The physical device has attributes that are adapted to the child node, that is, the spatial location or logical function corresponding to the target physical device is adapted to the attributes of the child node.
  • the attribute value corresponding to the child node is the corresponding spatial location of the target physical equipment in the workshop; for another example, if the child node is a node of the second type, that is, If the sub-node has logical function attributes, the attribute value corresponding to the sub-node is the corresponding process link of the target physical equipment in the production line/process.
  • the attribute value corresponding to the sub-node is the corresponding process link of the target physical equipment in the production line/process.
  • the prompt information when adding the identifier of the target entity device to the device asset list of the child node, it can be determined based on the identifier of the target entity device whether the target entity device has attributes that are adapted to the child node, and then determine If not, a prompt message is output for the user to confirm whether to establish an association between the child node and the target entity device.
  • the prompt information can be output in the form of a pop-up window or a floating layer.
  • the prompt information interface includes controls for performing confirmation operations and cancellation operations to determine whether to establish an association between the child node and the target physical device.
  • the user determines to establish an association between the child node and the target physical device, he can perform a trigger operation on the confirmation control and send a confirmation association instruction to the system. Further, upon receiving the confirmation association instruction, an association relationship between the child node and the target entity device may be established, and the identification of the target entity device may be added to the device asset list of the child node. If the user determines not to establish an association between the child node and the target physical device, he can perform a trigger operation on the cancel control and send a cancellation execution to the system, and then the association between the child node and the target physical device will not be established.
  • the specific method of obtaining the attributes of the target entity device is not limited.
  • the target entity device may be determined based on the identification of the target entity device.
  • Obtain the attribute information of the target physical device in real time for example, send an attribute information acquisition instruction to the target physical device in real time, so that the target physical device returns corresponding attribute information.
  • an attribute information input function may also be provided to obtain the input attribute information. For example, in response to the user performing an associated trigger action, the display Displays the device association interface.
  • the device association interface also includes attribute input items for users to input attribute information of the target device. Further optionally, when it is determined that the target physical device does not have attributes suitable for the child node, if the user performs a trigger operation on the confirmation control, the attribute information input interface can also be displayed for the user to input attribute information of the target physical 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's confirmation that the input is complete, an association between the target entity device and the child node is established. relationship, associate the attributes of the target entity device with the child node, and add the identity of the target entity device to the device asset list corresponding to the child node.
  • a device management model for managing the physical device is obtained. Further, after obtaining the device management model, a device management request may also be received.
  • the device management request includes a query condition, and the query condition includes at least one of a spatial location attribute to be queried and a logical function attribute to be queried. Based on this, when a device management request is received, at least one virtual management tree in the device management model can be traversed according to the spatial location attribute to be queried and/or the logical function attribute to be queried in the query conditions to obtain a query result that matches the query. List of device IDs for conditions.
  • the indicator 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 indicator data.
  • the specific method of obtaining the indicator data of the entity device to be managed in the specified entity space according to the device ID list is not limited.
  • the indicator data can be sent to the corresponding entity device according to the device ID in the device ID list.
  • training can also be performed in advance based on the indicator data of each physical device to obtain data modeling corresponding to the physical device.
  • each device in the device ID list can be The ID reads the indicator data in the corresponding data model; among them, the indicator data of the physical equipment includes but is not limited to the power consumption of the physical equipment, the number of downtimes, the length of downtime, etc.
  • the indicator data of the physical device to be managed is obtained, the operating status of the physical device to be managed can be analyzed based on the indicator data, and corresponding processing can be made if it is determined that the operating status is abnormal.
  • the embodiment of the present application also provides a space system export function.
  • the function controls on the space system page also include a space system export control.
  • the user selects the target system space, he can Trigger the space system export control to export the information of multiple physical devices associated with the selected target system space and the virtual management tree therein, as well as the cascading relationships between the physical devices.
  • a unique system ID SystemCod
  • SystemCod unique space ID
  • SpaceCode and create unique node IDs for all child nodes in each virtual management tree.
  • the space system export control in response to When the space system export control is triggered, you can query the space identification corresponding to the root node of all virtual management trees according to the system identification corresponding to the selected target system space; and then according to the root node and sub-node in each virtual management tree The cascading relationship, query the node identifiers corresponding to all sub-nodes in each virtual management tree; based on this, the device identifier associated with each sub-node can be obtained based on the association relationship between each sub-node and the physical device, so as to obtain the device identifier based on the device identifier Information about the physical device.
  • the specific form of the exported file type and file content is not limited.
  • the exported Excel table includes the identification corresponding to the physical device at each level; in another option, it can be exported through an Excel table.
  • it can also be exported in the form of a document.
  • the exported document includes a tree diagram corresponding to the structure of the virtual management tree, and each node in the diagram is an identifier of the corresponding physical device.
  • the above exported form and exported content are only illustrative and not limited thereto.
  • the exported content may also include the name of the physical device, attribute information, indicator data, etc., and the details may be determined according to the actual situation. Need determined.
  • FIG 2e is a schematic diagram of exporting the target space system according to different dimensions.
  • the user can select the type of export before deciding to export the target space system. It is assumed that the export dimension 1 is exported with the factory dimension, and the export dimension 2 is exported with the factory dimension. The workshop dimension is exported and the export dimension 3 is exported in the production line dimension. Based on this, users can select any export dimension as needed to export the corresponding content in the target space system in the form of Excel or documents.
  • the content corresponding to each workshop in the target system can be exported in the form of Excel or a document.
  • Excel a document
  • the embodiment of the present application also provides a space system import function.
  • the function controls on the space system page also include a space system import control.
  • the user can trigger the space system import control to import the pre-stored space system. Import the file of the target space system content into the edge computing device, and when the file is imported to the edge computing device, create the corresponding target space system in the service page, and render the corresponding virtual management in the file in the target space system In the tree.
  • the file import window can be displayed, and the user can import existing files into the edge computing device through the file import window; the edge computing device obtains the information of the imported file.
  • you can read the content in the file create the corresponding target space system in the service page based on the content in the file, and render the corresponding virtual management tree in the target space system for users to manage through the virtual management tree. Its associated devices are managed.
  • embodiments of the present application also provide a device management method to obtain indicator data of the physical device from multiple dimensions through the device management model in the above embodiment, so as to perform data analysis and management of the physical device.
  • Figure 3a shows this application Please provide a flow chart of the device management method provided by the embodiment, as shown in Figure 3a. The method includes:
  • the device management request includes query conditions.
  • the query conditions include at least one of a spatial location attribute to be queried and a logical function attribute to be queried;
  • the device management model corresponds to the specified entity space
  • At least one virtual management tree includes at least a first type of node with spatial location attributes and a second type of node with logical function attributes.
  • Different spatial location attributes correspond to different spatial locations in the specified entity space
  • different logical function attributes correspond to specified Different process links in the job process that exist in the physical space; the device management model is obtained by associating at least one node on the virtual management tree with multiple physical devices in the specified physical space.
  • the method of obtaining the device management model is not limited.
  • the device management model can be obtained through the method in the above device management model generation method. Based on this, as shown in Figure 3b, in the embodiment of the present application, before step P1, it also includes:
  • the target space system corresponds to the designated entity space, and the designated entity space includes multiple entity devices;
  • the at least one virtual management tree 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 at least includes first-type nodes with spatial location attributes and second-type nodes with logical function attributes.
  • different spatial location attributes correspond to different spatial locations in the specified entity space
  • different logical function attributes correspond to different process links in the job process existing in the specified entity space;
  • P03. Combine the spatial location attributes and logical function attributes of multiple physical devices, and associate multiple physical devices with nodes on at least one virtual management tree to obtain a multi-dimensional device management model.
  • step S1 to step S3 and step P1 to step P3 can be device A; for another example, the execution subject of step S1, step P1 and step P2 can be device A, and the execution subject of step S2 and step S3 and step P4 can be device A.
  • the execution subject can be device B; and so on.
  • FIG. 4 is a schematic structural diagram of the device management model generation device provided by the embodiment of the present application.
  • the device management model generation device includes a creation module 401, a first Generation module 402 and second generation module 403; wherein, the creation module 401 is used to respond to the creation operation of the space system to create a target space system, the target space system corresponds to the designated entity space, and the designated entity space includes multiple entity devices;
  • a generation module 402 is configured to generate at least one virtual management tree in the target space system in response to the generation operation of the management model.
  • the at least one virtual management tree at least includes first-type nodes with spatial location attributes and logical function attributes.
  • different spatial location attributes correspond to different spatial locations in the specified physical space
  • different logical function attributes correspond to different process links in the operation process existing in the specified physical space
  • the second generation module 403 is used to combine multiple physical devices.
  • the spatial location attributes and logical function attributes are used to associate multiple physical devices with nodes on at least one virtual management tree to obtain a multi-dimensional device management model.
  • FIG. 5 is a schematic structural diagram of the equipment management device provided by the embodiment of the present application.
  • the equipment 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.
  • the device management request includes query conditions, and the query conditions include at least one of spatial location attributes to be queried and logical function attributes to be queried; the query module 502 is used to traverse the device management model. At least one virtual management tree is used to obtain a list of device IDs that meet the query conditions.
  • the device management model corresponds to the specified physical space; the management module 503 is used to obtain the indicator data of the physical device to be managed in the specified physical space according to the device ID list, so as to obtain the indicator data of the physical equipment to be managed in the specified physical space according to the indicator.
  • the data is used for data analysis or management of the physical device to be managed; wherein, at least one virtual management tree includes at least a first type of node with spatial location attributes and a second type of node with logical function attributes, and different spatial location attributes correspond to the specified entity space. Different spatial locations and different logical function attributes correspond to different process links in the job process existing in the specified physical space; the equipment management model is obtained by associating nodes on at least one virtual management tree with multiple physical devices in the specified physical space. .
  • FIG. 6 is a schematic structural diagram of the edge computing device provided by the embodiment of the present application.
  • the edge computing device includes: a processor 61 and a memory storing computer programs. 62 and monitor 63.
  • the processor 61 and the memory 62 may be one or more.
  • Memory 62 is mainly used to store computer programs. These computer programs can be executed by the processor, causing the processor to The control processor 61 uses the edge computing device to implement corresponding functions and complete corresponding actions or tasks. In addition to storing computer programs, the memory may be configured to store various other data to support operations on the edge computing device used by the processor 61 . Examples of such data include data for operations on the edge computing device used by the processor 61 . Instructions for any application or method.
  • Memory 62 may 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, magnetic or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable Programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory magnetic memory
  • flash memory magnetic or optical disk.
  • the implementation form of the processor 61 is not limited.
  • it may be, but is not limited to, a CPU, a GPU, or an MCU.
  • 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 and complete corresponding actions or tasks. It is worth noting that depending on the implementation form of the edge computing device and the scenario it is in, the functions it needs to implement, the actions or tasks it completes will be different; accordingly, the computer program stored in the memory 62 will also be different. , and the processor 61 executes different computer programs to control the edge computing device to implement different functions and complete different actions or tasks.
  • the edge computing device may also include other components such as a communication component 64 and a power supply component 65 .
  • Figure 6 only schematically shows some components, which does not mean that the edge computing device only includes the components shown in Figure 6. According to different application requirements, the edge computing device can also include other components. The specific product form of the edge computing device can be seen Depends.
  • the processor 61 when the processor 61 executes the computer program in the memory 62, it is used to: respond to the creation operation of the space system, create a target space system, the target space system corresponds to the designated entity space, and the designated entity space includes Multiple physical devices; 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 at least includes a first type of node with a spatial location attribute and a third type of node with a logical function attribute.
  • different spatial location attributes correspond to different spatial locations in the specified physical space
  • different logical function attributes correspond to different process links in the operation process existing in the specified physical space
  • combining the spatial location attributes and logical function attributes of multiple physical devices associate multiple physical devices with nodes on at least one virtual management tree to obtain a multi-dimensional device management model.
  • the processor 61 when the processor 61 creates the target space system in response to the creation operation of the space system, the processor 61 is configured to: in response to the creation operation of the space system, display the space system page, and create at least one space system page on the space system page.
  • a base tree, at least one base tree and the space system page form the target space system.
  • the processor 61 when the processor 61 generates at least one virtual management tree in the target space system in response to the generation operation of the management model, the processor 61 is configured to: in response to the generation operation of the management model, display the target space system corresponding
  • the spatial 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 basic tree, the basic tree Perform an editing operation to obtain a virtual management tree containing a root node and at least one level of child nodes with attributes.
  • Each child Nodes have a spatial location attribute or a logical function attribute.
  • the processor 61 when the processor 61 responds to an editing trigger operation on any basic tree and performs an editing operation on the basic tree to obtain the corresponding virtual management tree, the processor 61 is configured to: respond to an editing operation on any basic tree.
  • the editing of the basic tree triggers the operation, displays the editing interface, and renders the basic tree to the editing interface to obtain the 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 of the tree to be edited , obtain the latest child node generated by the editing operation and its attributes and hierarchical relationships, and generate a virtual management tree based on the latest child nodes, their attributes and hierarchical relationships.
  • the editing operation includes at least one of adding sub-nodes, setting sub-node attributes, deleting sub-nodes, and adjusting sub-node hierarchical relationships.
  • the processor 61 obtains When editing the latest child node and its attributes and hierarchical relationships generated by the editing operation, it is used to: respond to the attribute setting operation of any child node in the tree to be edited, display the attribute setting interface, respond to the input operation on the attribute setting interface, obtain the child Attributes of the node; or in response to a node addition operation for any sub-node in the tree to be edited, adding a next-level sub-node below the sub-node, and in response to an attribute setting operation on the next-level sub-node, obtaining the next level attributes of the child node; or in response to the deletion operation for any child node in the tree to be edited, delete the child node and its attributes, and if the child node has subordinate child nodes
  • 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 means that all sub-nodes are The virtual management tree of the first type of node.
  • the second type of management tree refers to the virtual management tree in which all sub-nodes are second type nodes; when there is one virtual management tree, the virtual management tree is the third type of management tree.
  • the third type of management tree refers to a virtual management tree that contains both first type nodes and second type nodes.
  • the hierarchical relationship between sub-nodes reflects the hierarchical relationship or cascade relationship between attributes of sub-nodes at each level, and sub-nodes at the same level have spatial location attributes. and one or two types of logical functional attributes, and the same type of attributes has one or more types.
  • the processor 61 combines the spatial location attributes and logical function attributes of the multiple physical devices, and associates the multiple physical devices with nodes on at least one virtual management tree to obtain a multi-dimensional device.
  • it is used to: for each child node on each virtual management tree, in response to the association trigger operation on the child node, display the attributes and device association interface of the child node; in response to the input operation on the device association interface , obtain the identifier of the target entity device that needs to be associated with the child node, and add the identifier of the target entity device to the device asset list of the child node.
  • the target entity device has attributes that are adapted to the child node.
  • the processor 61 when the processor 61 adds the identification 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 a property suitable for the child node based on the identification of the target entity device. attribute; if not, output prompt information for the associated personnel to confirm whether to establish an association between the sub-node and the target entity device; when receiving the confirmation association instruction, the identification of the target entity device Added to the device asset list of the child node.
  • the processor 61 is further configured to: receive a device management request, where the device management request includes query conditions, and the query conditions include the spatial location attributes to be queried and the logical function attributes to be queried. At least one; traverse at least one virtual management tree in the device management model to obtain a list of device IDs that meet the query conditions; obtain the indicator data of the entity device to be managed in the specified entity space according to the device ID list, and obtain the indicator data of the entity to be managed in the specified entity space based on the indicator data Equipment for data analysis or management.
  • embodiments of the present application also provide a computer-readable storage medium storing a computer program.
  • the computer program When executed by a processor, it causes the processor to implement each step in the above method embodiment.
  • embodiments of the present application also provide a computer program product, which includes a computer program/instruction.
  • the computer program/instruction When executed by a processor, it causes the processor to implement each step in the above method embodiment.
  • the communication component in the above embodiment is configured to facilitate wired or wireless communication between the device where the communication component is located and other devices.
  • the device where the communication component is located can access wireless networks based on communication standards, such as WiFi, 2G, 3G, 4G/LTE, 5G and other mobile communication networks, or a combination thereof.
  • the communication component receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communication component further includes a near field communication (NFC) module to facilitate short-range communication.
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • the display in the above embodiment includes a screen, and the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide action.
  • the power supply component in the above embodiment provides power for various components of the device where the power supply component is located.
  • a power component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device in which the power component resides.
  • the audio components in the above embodiments may be configured to output and/or input audio signals.
  • the audio component includes a microphone (MIC), and when the device where the audio component is located is in an operating mode, such as call mode, recording mode, and voice recognition mode, the microphone is configured to receive an external audio signal.
  • the received audio signal may be further stored in memory or sent via a communications component.
  • the audio component further includes a speaker for outputting audio signals.
  • embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt an entirely hardware embodiment, an entirely software embodiment, or an implementation combining software and hardware aspects. Example form. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory that causes 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 an article of manufacture including the instruction means, the instructions
  • the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device.
  • Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Tourism & Hospitality (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Educational Administration (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • Game Theory and Decision Science (AREA)
  • Development Economics (AREA)
  • Manufacturing & Machinery (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本申请实施例提供一种设备管理模型生成与设备管理方法、设备及存储介质。在本申请实施例中，用户可以创建与指定实体空间对应的目标空间系统，以在目标空间系统中创建与指定实体空间中对应的虚拟管理树；进一步，通过虚拟管理树上具有的位置空间属性和逻辑功能属性的节点与实体空间中的实体设备进行关联，可以使虚拟管理树上的节点指向实体空间中的不同空间位置以及指向实体空间中不同的流程环节，生成可以从空间位置以及逻辑功能不同维度对实体设备进行管理的设备管理模型。并且，用户可以获取上述生成的设备管理模型，并通过获取的设备管理模型从空间位置和逻辑功能多个维度对实体空间中的实体设备实体进行管理，管理方式更丰富多样。

Description

设备管理模型生成与设备管理方法、设备及存储介质
本申请要求于2022年03月24日提交中国专利局、申请号为202210303417.X、申请名称为“设备管理模型生成与设备管理方法、设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及边缘云技术领域，尤其涉及一种设备管理模型生成与设备管理方法、设备及存储介质。
背景技术
在各种生产企业中通常会涉及大量生产设备，这些生产设备是生产企业的重要资产，因此有必要对这些设备资产进行有效管理，以在资产建设、维护中减少维护成本，减少设备停机时间，进而提高设备运营效率，提高企业的整体生产效率。
在现有设备管理方案中倾向于对物理世界的映射，即将各生产设备与其所属的车间进行关联登记。例如，管理人员在管理设备时，会记录空压机1和空压机2均放置在第十车间中，用户通过查询该登记信息即可找到第十车间中的空压机1和空压机2并对其进行管理。这种设备资产管理方式仅支持从车间维度的设备管理，无法满足多维度的设备管理需求。
发明内容
本申请的多个方面提供一种设备管理模型生成与设备管理方法、设备及存储介质，用以从空间位置和逻辑功能多维度对实体空间中的实体设备进行管理。
本申请实施例提供一种设备管理模型生成方法，包括：响应于空间系统的创建操作，创建目标空间系统，所述目标空间系统对应于指定实体空间，所述指定实体空间包括多个实体设备；响应于管理模型的生成操作，在所述目标空间系统中生成至少一棵虚拟管理树，所述至少一棵虚拟管理树至少包括具有空间位置属性的第一类节点和具有逻辑功能属性的第二类节点，不同空间位置属性对应所述指定实体空间中的不同空间位置，不同逻辑功能属性对应所述指定实体空间中存在的作业流程中的不同流程环节；结合所述多个实体设备的空间位置属性和逻辑功能属性，将所述多个实体设备与所述至少一棵虚拟管理树上的节点进行关联，以得到多维度的设备管理模型。
本申请实施例还提供一种设备管理方法，包括：接收设备管理请求，所述设备管 理请求包括查询条件，所述查询条件包括待查询空间位置属性和待查询逻辑功能属性中的至少一种；遍历设备管理模型中的至少一棵虚拟管理树，以得到符合所述查询条件的设备ID列表，所述设备管理模型对应指定实体空间；根据所述设备ID列表获取所述指定实体空间中待管理实体设备的指标数据，根据所述指标数据对所述待管理实体设备进行数据分析或管理；其中，所述至少一棵虚拟管理树至少包括具有空间位置属性的第一类节点和具有逻辑功能属性的第二类节点，不同空间位置属性对应所述指定实体空间中的不同空间位置，不同逻辑功能属性对应所述指定实体空间中存在的作业流程中的不同流程环节；所述设备管理模型是所述至少一棵虚拟管理树上的节点与所述指定实体空间中多个实体设备进行关联得到的。
本申请实施例还提供一种设备管理模型生成装置，包括：创建模块，用于响应于空间系统的创建操作，以创建目标空间系统，所述目标空间系统对应于指定实体空间，所述指定实体空间包括多个实体设备；第一生成模块，用于响应于管理模型的生成操作，在所述目标空间系统中生成至少一棵虚拟管理树，所述至少一棵虚拟管理树至少包括具有空间位置属性的第一类节点和具有逻辑功能属性的第二类节点，不同空间位置属性对应所述指定实体空间中的不同空间位置，不同逻辑功能属性对应所述指定实体空间中存在的作业流程中的不同流程环节；第二生成模块，用于结合所述多个实体设备的空间位置属性和逻辑功能属性，将所述多个实体设备与所述至少一棵虚拟管理树上的节点进行关联，以得到多维度的设备管理模型。
本申请实施例还提供一种设备管理装置，包括：接收模块，用于接收设备管理请求，所述设备管理请求包括查询条件，所述查询条件包括待查询空间位置属性和待查询逻辑功能属性中的至少一种；查询模块，用于遍历设备管理模型中的至少一棵虚拟管理树，以得到符合所述查询条件的设备ID列表，所述设备管理模型对应指定实体空间；管理模块，用于根据所述设备ID列表获取所述指定实体空间中待管理实体设备的指标数据，以根据所述指标数据对所述待管理实体设备进行数据分析或管理；其中，所述至少一棵虚拟管理树至少包括具有空间位置属性的第一类节点和具有逻辑功能属性的第二类节点，不同空间位置属性对应所述指定实体空间中的不同空间位置，不同逻辑功能属性对应所述指定实体空间中存在的作业流程中的不同流程环节；所述设备管理模型是所述至少一棵虚拟管理树上的节点与所述指定实体空间中多个实体设备进行关联得到的。
本申请实施例还提供一种边缘计算设备，包括：显示器、处理器以及存储有计算机程序的存储器，所述处理器用于执行所述计算机程序，以用于执行所述方法中的任 一项步骤。
本申请实施例还提供一种存储有计算机程序的计算机可读存储介质，当所述计算机程序被处理器执行时，致使所述处理器实现所述中的任一项步骤。
本申请实施例还提供一种计算机程序产品，包括计算机程序/指令，当计算机程序/指令被处理器执行时，致使处理器实现所述方法中的任一项步骤。
在本申请实施例中，用户可以创建与指定实体空间对应的目标空间系统，以在目标空间系统中创建与指定实体空间中对应的虚拟管理树；进一步，通过虚拟管理树上具有的位置空间属性和逻辑功能属性的节点与实体空间中的实体设备进行关联，可以使虚拟管理树上的节点指向实体空间中的不同空间位置以及指向实体空间中不同的流程环节，生成可以从空间位置以及逻辑功能不同维度对实体设备进行管理的设备管理模型。并且，用户可以获取上述生成的设备管理模型，并通过获取的设备管理模型从空间位置和逻辑功能多个维度对实体空间中的实体设备实体进行管理，管理方式更丰富多样。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1为本申请实施例提供的一种设备管理模型生成方法的流程图；
图2a为本申请实施例提供的一种用于创建目标空间系统的服务页面的示意图；
图2b为本申请实施例提供的一种用于展示基础树的空间系统页面的示意图；
图2c为本申请实施例提供的一种用于对基础树进行编辑的编辑界面的示意图；
图2d为本申请实施例提供的一种对基础树进行编辑后的示意图；
图2e为本申请实施例提供的一种导出空间系统操作界面的示意图；
图3a为本申请实施例提供的一种设备管理方法的流程图；
图3b为本申请实施例提供的另一种设备管理模型生成方法的流程图；
图4为本申请实施例提供的一种设备管理模型生成装置的结构示意图；
图5为本申请实施例提供的一种设备管理装置的结构示意图；
图6为本申请实施例提供的一种边缘计算设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合本申请具体实施例及相应的附图对本申请技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
在生产企业对生产设备进行管理过程中，通常采用物理世界映射的方式，将各生产设备与其所属的车间进行关联登记，以确定各生产设备与各车间在物理空间中的所属关系，进而实现对各车间中的生产设备进行管理和维护，然而，仅从物理空间这一维度考虑，并不能很好的满足对大量生产设备的管理需求。在企业生产场景中，通常会涉及工厂、车间、工位、产线/工艺以及产线/工艺上各道工序所使用的生产设备等生产结构，为了更清楚的了解生产设备的运行状态、资源消耗情况等信息，不仅要了解各生产设备所属的车间，更多情况下，需要从产线/工艺等维度了解各生产设备在当前所处的工序下对应的运行状态、资源消耗情况等。因此，结合生产企业的实际管理需求，有必要提供一种即能从物理上的空间位置维度、又能从产线/工艺等逻辑功能维度对生产设备进行管理的方案。
为此，在本申请实施例中，提供一种新型的设备管理模型，该设备管理模型支持从多维度对各行业中的实体设备进行管理，既能从不同粒度的空间位置维度对实体设备进行管理，也能够从不同粒度的逻辑功能维度对实体设备进行管理。本申请实施例提供的设备管理模型可应用于各种涉及实体设备需要管理的行业，例如可以是各种生产行业，也可以是物流行业、仓储管理行业等。本申请各实施例中的实体设备是指各行业中需要被管理的物理设备，根据应用行业的不同，这些实体设备也会有所不同。以生产行业为例，这些实体设备可以是各种生产设备，进一步以制衣行业为例，这些实体设备涉及断布机、熨烫机、印染机、缝纫机等生产设备。以物流行业为例，这些实体设备涉及封口设备、贴标设备、装卸设备、搬运机器人、货物运输设备等各种物流设备。
进一步，为了方便通过该新型的设备管理模型对各行业中的实体设备进行多维度管理，本申请实施例可以提供一种边缘计算设备，由该边缘计算设备负责生成该新型的设备管理模型并基于该设备管理模型进行设备管理。本申请实施例提供的边缘计算设备是一种可以部署在云网络边缘位置的具备计算、网络、存储、安全等能力的计算设备。在实现形态上，该边缘计算设备可以实现为一台或多台服务器以及部署在服务器上的软件程序，这些服务器和软件程序可被一同打包作为一种边缘部署形态的云产品(即边缘计算设备)提供给企业用户。在边缘计算设备中，通过运行相应软件程序可面向企业用户提供设备管理模型生成服务以及基于所生成的设备管理模型的设备管理服务。企业用户可以将边缘计算设备部署到企业现场环境中，也可以部署到靠近企业现场环境的边缘云系统中的机房或互联网数据中心(Internet Data Center，IDC)中，对此不做限定。无论部署位置在哪里，企业用户可以通过该边缘计算设备提供的设备管理模型生成服务，生成与其应用需求适配的设备管理模型，并且可基于该设备管理模型从不同粒度的空间位置以及逻辑功能等多维度对企业内部各种实体设备进行管理。在本申请下面实施例中，将对设备管理模型的生成过程以及基于设备管理模型的设备管理过程进行详细描述。
本申请实施例提供一种设备管理模型生成方法，通过该方法可以生成能够从多维度管理实体设备的设备管理模型，以供各行业的开发人员或一线操作人员使用，对相关实体设 备进行管理。图1为本申请实施例提供的设备管理模型生成方法的流程图，如图1所示，方法包括：
S1、响应于空间系统的创建操作，创建目标空间系统，目标空间系统对应于指定实体空间，指定实体空间包括多个实体设备；
S2、响应于管理模型的生成操作，在目标空间系统中生成至少一棵虚拟管理树，至少一棵虚拟管理树至少包括具有空间位置属性的第一类节点和具有逻辑功能属性的第二类节点，不同空间位置属性对应指定实体空间中的不同空间位置，不同逻辑功能属性对应指定实体空间中存在的作业流程中的不同流程环节；
S3、结合多个实体设备的空间位置属性和逻辑功能属性，将多个实体设备与至少一棵虚拟管理树上的节点进行关联，以得到多维度的设备管理模型。
在本实施例中，提出空间系统的概念，空间系统是一种逻辑管理空间，可由用户根据自己的管理需求自行定义。假设用户对指定实体空间中的实体设备具有管理需求，则可以针对该指定实体空间建立对应的空间系统，该空间系统作为一种逻辑管理空间，可以承载该指定实体空间中与用户管理需求适配的空间位置以及该指定实体空间中存在的与用户管理需求适配的作业流程以及作业流程中的流程环节；进一步，还可以承载这些空间位置以及流程环节之间的关联关系，以便形成虚拟管理树。其中，这些与用户管理需求适配的空间位置和流程环节也可以称为空间系统中的空间资源或资源对象。如果用户对不同实体空间中的实体设备均具有管理需求，则可以针对不同实体空间创建不同空间系统，每个空间系统具有唯一标识，可选地，可以将空间系统的唯一标识称为系统代码(SystemCode)，用户通过系统代码可以查询到对应的空间系统。
在本申请实施例中，设备管理模型生成服务被部署并被启动之后，如图2a所示，可以展示服务页面，在该服务页面上包括用于创建空间系统的功能控件，以供用户在需要时能够发起创建空间系统的操作。当用户对指定实体空间中的实体设备具有管理需求时，可以通过该功能控件发起空间系统创建操作。相应地，在响应到用户触发该功能控件的情况下，可以创建与指定实体空间对应的空间系统，并将创建的空间系统渲染至功能控件下方所在区域。为便于描述和区分，在本实施例中，将与指定实体空间对应的空间系统称为目标空间系统。在本申请实施例中，不限定指定实体空间的具体类型，根据应用行业的不同，对应的实体空间也会不同。例如，在生产制造行业，指定实体空间可以为工厂、车间或多个车间或多个工厂等；又例如，在仓储物流行业，指定实体空间可以为仓库，等等。例如，当需要对一个工厂内的所有实体设备进行管理时，指定实体空间为一个工厂；当需要对一个工厂的某个车间或某几个车间内的所 有实体设备进行管理时，指定实体空间为一个车间或几个车间；当需要对跨不同区域的多个工厂内的所有实体设备进行管理时，指定实体空间为跨不同区域的多个工厂，等等。
在得到目标空间系统之后，可以在目标空间系统中生成至少一个虚拟管理树，通过这些虚拟管理树上的节点对指定实体空间中的实体设备进行管理。每棵虚拟管理树具有唯一标识，可选地，可以将虚拟管理树的唯一标识称为空间代码(spaceCode)，用户通过空间代码可以查询到对应的虚拟管理树。具体地，可响应于管理模型的生成操作，在目标空间系统中生成至少一棵虚拟管理树。在本申请实施例中，为了能够从多维度对实体设备进行管理，目标空间系统中的虚拟管理树上至少包括两类节点，即具有空间位置属性的第一类节点和具有逻辑功能属性的第二类节点。在本实施例中，空间位置属性和逻辑功能属性是两大类属性，在每种属性下面还可以具有不同粒度的属性，也就是说，从属性粒度来看，空间位置属性具有多个，逻辑功能属性也具有多个；进一步，在同一粒度上，空间位置属性也可以有多个，逻辑功能属性也可以有多个。举例说明，工厂是一个粒度，车间是一个粒度，在工厂这一粒度上，又可以存在工厂1-工厂n，在车间这个粒度上，又可以存在车间1-车间m；同理，产线是一个粒度，工序是一个粒度，在产线这一粒度上，可存在产线1-产线k，在工序这个粒度上，又可以存在工序1-工序p。其中，n、m、k、p均为大于等于2的自然数。需要说明的是，这些属性粒度和同粒度上的属性划分，是根据用户的管理需求划分的，可能与实际生产中存在的位置空间的粒度和数量以及产线、工序的粒度和数量相同，也可以不同。
在本申请实施例中，第一类节点的数量为一个或多个，且在为多个的情况下，不同第一类节点对应的空间位置属性可以相同，也可以不同；同理，第二类节点的数量为一个或多个，且在为多个的情况下，不同第二类节点对应的逻辑功能属性可以相同，也可以不同。其中，不同空间位置属性对应指定实体空间中的不同空间位置，也就是说，对应不同空间位置属性的第一类节点代表指向实体空间中的不同空间位置。例如，具有不同空间位置属性的两个节点，一个节点代表车间1，另一个节点可能代表车间2，或者一个节点代表车间1，另一节点代表工厂1。相应地，不同逻辑功能属性对应指定实体空间中存在的作业流程中的不同流程环节，也就是说，对应不同逻辑功能属性的第二类节点代表指向不同的流程环节。例如，具有不同逻辑功能属性的两个节点，一个节点代表工序1，另一个节点可能代表工序2，或者一个节点代表产线1，另一个节点可能代表工序2。
另外，本申请实施例并不限定目标空间系统中包含的虚拟管理树的数量，可以是一棵，也可以是多棵。其中，对于目标空间系统包含一棵虚拟管理树的情况，该虚拟管理树同时包括两种类型的节点，即同时包括第一类节点和第二类节点，属于同时兼具空间位置属性和逻辑功能属性的混合树。对于目标空间系统包含两棵或两棵以上虚拟管理树的情况，存在以下两种情况：
情况1：这些虚拟管理树包括第一类管理树和第二类管理树；其中，第一类管理树上的节点全是第一类节点，第二类管理树上的节点全是第二类节点。
情况2：这些虚拟管理树全部是第三类管理树，即第三类管理树上及具有第一类节点有具有第二类节点。
情况3：这些虚拟管理树同时包括第一类管理树、第二类管理树和第三类管理树。
无论是上述哪种情况，可以获取用户的设备管理需求，根据该设备管理需求，同时结合虚拟管理树上各节点的属性，以及指定实体空间中多个实体设备的空间位置属性和逻辑功能属性，将多个实体设备与至少一棵虚拟管理树上的节点进行关联，最终得到多维度的设备管理模型。在本实施例中，每个实体设备同时具备空间位置属性和逻辑功能属性，这些空间位置属性和逻辑功能属性也是分粒度且同一粒度上也会存在多个不同的属性。例如，在一种情况下，设备管理需求是对第一空间位置属性上的设备进行管理，则可以将具有第一空间位置属性的实体设备与具有第一空间位置属性的节点进行关联；在另一种情况下，设备管理需求是对第一空间位置属性上具有第一逻辑功能属性的实体设备进行管理，则可以将第一空间位置属性上具有第一逻辑功能属性的实体设备与具有第一逻辑功能属性的节点进行关联，例如，设备管理需求是对车间1中的设备A进行管理，则可以将空间位置属性为车间1的节点与设备A进行关联；在另一种情况下，设备管理需求是对第一空间位置属性上具有第一逻辑功能属性的实体设备进行管理，则可以将第一空间位置属性上具有第一逻辑功能属性的实体设备与具有第一逻辑功能属性的节点进行关联，例如，设备管理需求是对车间2中负责印刷工序的设备B进行管理，则可以将逻辑功能属性为印刷工序的节点与设备B进行关联，等等。
在本申请实施例中，用户通过部署具有设备管理模型生成服务的边缘设备，可以通过边缘设备创建与指定实体空间对应的目标空间系统，以在目标空间系统中创建与指定实体空间中对应的虚拟管理树；进一步，通过虚拟管理树上具有的位置空间属性和逻辑功能属性的节点与实体空间中的实体设备进行关联，可以使虚拟管理树上的节点指向实体空间中的不同空间位置以及指向实体空间中不同的流程环节，生成可以从 空间位置以及逻辑功能不同维度对实体设备进行管理的设备管理模型。并且，边缘设备还提供有设备管理服务，基于该设备管理服务，用户可以获取上述生成的设备管理模型，并通过获取的设备管理模型从空间位置和逻辑功能多个维度对实体空间中的实体设备实体进行管理，管理方式更丰富多样。
在本申请实施例中，不限定创建目标空间系统的具体方式，可选地，在响应到用户对服务页面上的“创建空间系统”功能控件执行触发操作的情况下，如图2b所示，可显示空间系统页面，并在该空间系统页面上创建至少一棵基础树；其中，至少一棵基础树和空间系统页面形成本实施例的目标空间系统。也就是说，本实施例的目标空间系统在具体实现上是一个具有管理功能的页面，且在该页面上具有至少一棵基础树。在本申请实施例中，如图2b所示，每棵基础树可以包括根节点和属性为空的至少一级子节点。需要说明的是，本申请实施例不限定至少一棵基础树的具体结构，至少一棵基础树可以具有完全相同的结构，即具有相同的节点层级以及在每层上包括相同数量的节点，也可以具有不同的结构；其中，每棵基础树上的节点具有对应的属性，但是在初始阶段，每个节点的属性为空。另外，需要说明的是，在本申请实施例中，也不限定基础树的数量，在不同空间系统中，基础树的数量可以相同，也可以不相同。另外，允许用户对这些基础树进行删除或增加。具体地，如图2b所示，在空间系统页面中，基础树所在区域中包含有“添加”控件和“删除”控件，用户触发“添加”控件可以继续在基础树所在区域新增基础树，以及在选中任一课基础树的情况下，触发“删除”控件可以将选中的基础树删除。进一步可选地，在添加基础树的过程中，还可以展示基础树设置页面，用户可以通过该基础树设置页面设置基础树的结构信息，即用户可以设置基础树的层数、每层包含的节点数以及节点之间的父子关系等，进而根据用户设置的基础树的结构信息生成新的基础树并呈现在空间系统页面上。
在本申请实施例中，这些基础树是生成虚拟管理树的基础，且允许对这些基础树进行编辑，以便生成对应的虚拟管理树。可选地，用户可以对目标空间系统中的基础树进行编辑操作，以便于在基础树的基础上生成虚拟管理树。在一可选实施例中，目标空间系统中的这些基础树支持交互操作，用户可以触发至少一棵基础树对其进行编辑以生成对应的虚拟管理树。在另一可选实施例中，每个基础树所在区域内显示有编辑控件，用户可以通过触发该编辑控件发起对某棵基础树的编辑操作。在此说明，在本申请各实施例中，无论用户触发的对象是页面、基础树还是控件，其触发方式可以采用但不限于以下任一种：点击、双击、长按、触控、鼠标悬停等。基于此，可响应用户对任一棵基础树发起的编辑触发操作，再响应到对任一棵基础树触发编辑操作的 情况下，如图2c所示，可显示待编辑的基础树对应的编辑界面，并将该基础树渲染至编辑界面上以得到待编辑树；其中，将基础树渲染至编辑界面上的过程包括：在显示屏幕上渲染一个画布(canvas)，该画布提供全屏、缩放等基础交互工具，这些基础交互工具位于工具区内，该画布还包括一个编辑区；之后可以根据基础树的结构，即根节点与各级子节点之间的父子关系(或称为层级关系)，通过递归的方式从根节点开始，按照层级在编辑区内渲染出一个个节点；在此过程中，为了方便用户对基础树进行编辑操作，可将各节点与预设编辑操作对应的编辑事件，例如点击(click)事件、拖动(drag)事件等进行绑定，绑定编辑事件之后的节点支持用户对其进行对应的编辑操作，例如用户可以对节点进行点击或拖动操作等。在本实施例中，对同一棵树(包括基础树、待编辑树或虚拟管理树)而言，将根节点之外的节点称为子节点。
其中，在编辑界面上的基础树处于可编辑状态，故称之为待编辑树，用户对待编辑树进行各种编辑操作之后可得到虚拟管理树。用户可以触发任一子节点对其进行编辑操作，可选地，子节点绑定的事件包括但不限于属性设置事件、节点添加事件、节点删除事件以及拖拽事件等。这些编辑事件对应不同的编辑操作，通过不同的编辑操作，可以对该子节点进行不同类型的编辑操作。例如，对任一子节点，可以通过属性编辑操作触发属性设置事件，从而编辑子节点的属性，也可以通过节点添加操作触发节点添加事件，从而为该子节点添加下级子节点，也可以通过节点删除操作触发节点删除事件，从而删除该子节点，也可以通过拖拽操作触发拖拽事件，从而调整该子节点与其它子节点或根节点之间的父子关系等。这些编辑操作或事件会产生最新的子节点及其属性和层级关系，基于此，在响应到用户对待编辑树的编辑操作的情况下，可以获取编辑操作产生的最新子节点及其属性和层级关系，并根据最新子节点及其属性和层级关系，生成虚拟管理树。
在本申请实施例中，不限定用户对待编辑树中的每个子节点可执行的编辑操作的种类以及执行编辑操作的具体方式。可选地，编辑操作可以为增加子节点、设置子节点属性、删除子节点、调整子节点层级关系中的至少一种；进一步可选地，在用户对待编辑树中子节点执行上述任一操作的时，可通过触发任一子节点以触发对应的事件，以在对应类型事件被响应的情况下，执行对应类型的编辑操。例如，在响应到用户针对待编辑树中任一子节点的属性设置操作的情况下，可触发子节点对应的属性设置事件以显示属性设置界面；进一步，用户可以在该属性设置界中输入子节点对应的属性信息，则在响应到用户在该属性设置界面上的输入操作的情况下，可以获取子节点的属性。又例如，在响应到用户针对待编辑树中任一子节点的节点添加操作的情况下， 可触发子节点对应的节点添加事件，以在子节点下面添加下一级子节点。图2d为在基础树的两个子节点下面分别添加下一级子节点后的示意图，如图2d所示，该基础树根节点下一级子节点分别为子节点1、子节点2和子节点3，用户分别在子节点1下面添加下一级子节点11、子节点12和子节点13，以及在子节点3下面添加下一级子节点31和子节点32。进一步，用户还可以对新添加的下一级子节点执行属性设置操作，以对其进行设置属性；基于此，在响应到用户对下一级子节点的属性设置操作的情况下，可触发下一级子节点对应的属性设置事件以显示属性设置界面；进一步，用户可以在该属性设置界中输入下一级子节点对应的属性信息，则在响应到用户在该属性设置界面上的输入操作的情况下，可以获取下一级子节点对应的属性。又例如，在响应到用户针对待编辑树中任一子节点的删除操作的情况下，可以触发子节点对应的节点删除事件，以删除子节点及其属性，并在子节点具有下级子节点的情况下，将子节点的下级子节点及其属性删除。又例如，在响应到用户针对待编辑树中任一子节点的拖拽操作的情况下，可以触发子节点对应的拖拽事件；进一步，根据子节点被拖拽到的目标位置，可以确定子节点最新的父节点和/或子节点，并根据最新的父节点和/或子节点修改子节点的层级关系。
在本申请实施例中，不限定执行上述编辑操作的具体方式，可选地，在任一子节点被触发的情况下，可以通过弹窗或浮层的形式显示功能列表，列表中可以包含“属性设置”、“节点新增”、“节点删除”或者“节点调整”等功能标签，用户可以触发任一标签编从而发起对应的编辑操作。例如，当用户触发“属性设置”时可显示属性设置界面，以供用户输入节点的属性信息；当用户触发“节点新增”标签时，可以为当前子节点增加下一级子节点；当用户触发“节点删除”标签时，可以删除当前子节点及其属性，或者连通当前子节点的下级子节点及其属性一并删除；当用户触发“节点调整”标签时，当前子节点变为可被拖动状态，用户可将当前节点拖动到任一子节点或根节点的下一级作为其子节点，并根据最新的父节点和/或子节点修改子节点的层级关系等。当然，上述编辑方式仅为示例性说明，并不限于此。在待编辑树中的子节点支持直接编辑操作的情况下，用户可以直接触发任一子节点以发起对应的编辑操作。例如，在响应到用户单击任一子节点的情况下，可以自动为其增加下一级子节点；在响应到用户双击任一子节点的情况下，可以直接删除该子节点，或者连同当前子节点的下级子节点及其属性一并删除；子节点默认可被拖动，用户可以直接将当前子节点拖动到任一子节点或根节点的下一级作为其子节点，并根据最新的父节点和/或子节点修改子节点的层级关系等；又例如，在选中任一子节点的情况下，也可以通过快捷键 为选中的子节点增加下一级子节点或删除被选中的子节点等等；当然，也可以通过上述任两种或多种组合的方式对待编辑树进行编辑，生成对应的虚拟管理树，具体可根据实际需求确定，在此不做限定。
在此说明，对一棵待编辑树上同一层上的各子节点的属性可以是某个粒度的空间位置属性，也可以是某个粒度的逻辑功能属性，还可以部分子节点是某个粒度的空间位置属性，部分子节点是某个粒度的逻辑功能属性，同一层上的各子节点的属性类型可以相同也可以不同，对于各子节点设置哪种属性以及哪个粒度上的属性具体可根据管理需求而定，对此不做限定。例如，假设第一层具有两个子节点，为第一层的某个子节点设置其具有空间位置属性，且其空间位置属性具体为车间1，为第一层的另一个子节点设置其具有空间位置属性，且其空间位置属性具体为车间2；进一步，可以为第二层子节点设置逻辑功能属性，假设为车间1这个子节点的下一级子节点设置逻辑功能属性，且其逻辑功能属性具体为产线1对应的工序1，为车间2这个子节点的下一级子节点设置逻辑功能属性，且其逻辑功能属性具体为产线2对应的工序2。又例如，假设第一层具有两个子节点，为第一层的某个子节点设置其具有空间位置属性，且其空间位置属性具体为车间1，为第一层的另一个子节点设置其具有逻辑功能属性，且其逻辑功能属性具体为产线1对应的工序1；进一步，可以为车间1这个子节点的下一级子节点设置逻辑功能属性，且其逻辑功能属性具体为产线2对应的工序2，为工序1这个子节点的下一级子节点设置空间位置属性，且其空间位置属性具体为车间2，等等。
在本申请实施例中，生成的虚拟管理树不是按照指定实体空间在物理世界中的实际位置映射而来的，而是根据企业的工厂、车间、产线/工艺以及产线/工艺上各道工序所使用的实体设备对应的空间位置和逻辑功能得到的。因此，目标空间系统中的至少一棵虚拟管理树至少包括两类节点，即具有空间位置属性或者逻辑功能属性的两类节点，根据节点的类型，可以对虚拟管理树进行分类。在本申请实施例中，在对虚拟管理树分类时，重点考虑子节点，不考虑根节点。基于此，将全部子节点均具有空间位置属性的虚拟管理树称为第一类管理树、将全部子节点均具有逻辑功能属性的虚拟管理树称为第二管理树，以及将部分部子节点具有空间位置属性、部分子节点具有逻辑功能属性的虚拟管理树称为第三类管理树。进一步，本申请实施例也不限定虚拟管理树的数量以及虚拟管理树的类型，可选地，在虚拟管理树为多棵的情况下，多棵虚拟管理树中可以包括第一类管理树和第二类管理树，或者多棵虚拟管理树均为第三类管理树；在虚拟管理树为一棵的情况下，虚拟管理树为第三类管理树。对任一棵虚拟管 理树而言，子节点之间的层级关系反映各层子节点具有的属性之间的层级关系或级联关系，同一层子节点具有空间位置属性和逻辑功能属性中的一类或两类，同一类属性可以具有一种或多种。关于每棵虚拟管理树的具体结构，可以根据企业的工厂、车间、产线/工艺以及产线/工艺上各道工序所使用的实体设备对应的空间位置和逻辑功能确定。这样，将生成的虚拟管理树作为企业管理工厂、车间、产线/工艺、实体设备的设备管理模型，便可以方便直观的从产线/工艺的角度了解到实体设备的使用状态。
在本申请实施例中，不限定每棵虚拟管理树中子节点对应的空间位置属性和逻辑功能属性的个数，可选地，空间位置属性和逻辑功能属性均可以为一个或多个。在位置空间属性为多个的情况下，每个空间位置属性对应指定实体空间中的一个空间位置，不同空间位置属性对应不同空间位置；当然，具有相同空间位置属性的第一类节点对应该指定实体空间中的相同空间位置，具有不同空间位置属性的第一类节点对应该指定实体空间中的不同空间位置。例如，设备1和设备2均位于车间A中，则与设备1和设备2分别关联的子节点1和子节点2均为第一类节点，且对应相同的空间位置为车间A；又例如，设备3位于车间B中，设备4位于车间C中，则与设备3和设备4分别关联的子节点3和子节点4均为第一类节点，但对应不同的空间位置，分别为车间B和车间C。在逻辑功能属性为多个的情况下，每个逻辑功能属性对应指定实体空间中作业流程中的一个流程环节，不同逻辑功能属性对应指定实体空间中作业流程中的不同的流程节点；当然，具有相同逻辑功能属性的第二类节点对应指定实体空间中作业流程中相同的流程环节，具有不同逻辑功能属性的第二类节点对应指定实体空间中作业流程中不同的流程环节。例如，设备1和设备2均为印刷产线中负责印刷工序的设备，则与设备1和设备2分别关联的子节点1和子节点2均为具有印刷逻辑功能属性的第二类节点，且对应相同的流程节点为印刷工序；又例如，设备3为印刷产线中负责临摹工序的设备，设备4为印刷产线中负责生切工序的设备，则与设备3关联的子节点3为具有临摹逻辑功能属性的第二类节点，对应的流程环节为临摹工序，与设备4关联的子节点4为具有生切逻辑功能属性的第二类节点，对应的流程环节为生切工序。需要说明的是，本申请实施例中的流程环节的切分粒度是根据设备管理需求确定的，与实际作业流程中的流程关节可以相同也可以不同，在此不做限定。
在本申请实施例中，虚拟管理树上的每个子节点还可以绑定设备关联事件，以供用户将虚拟管理树中的子节点与实体设备进行关联；进一步可选地，虚拟管理树中的子节点还对应有设备资产列表，其中包含与子节点关联的实体设备的标识，针对每一个子节点，当用户为其关联一个实体设备的情况下，该被关联的实体设备的标识将被 添加到当前子节点对应的设备资产列表中。基于此，在结合多个实体设备的空间位置属性和逻辑功能属性，将多个实体设备与至少一棵虚拟管理树上的节点进行关联时，可以针对每一棵虚拟管理树上的每个子节点执行关联触发操作，以触发子节点对应的设备关联事件；基于此，在响应到针对子节点的关联触发操作的情况下，可以触发设备关联事件并显示子节点具有的属性和设备关联界面，在设备关联界面上包含至少一个输入项，以供用户输入目标实体设备的标识。进一步，在响应到设备关联界面上的输入操作的情况下，可以获取需要与子节点关联的目标实体设备的标识，并将目标实体设备的标识添加至子节点的设备资产列表中；其中，目标实体设备具有与子节点适配的属性，即目标实体设备对应的空间位置或者逻辑功能与子节点的属性适配。例如，子节点为第一类节点，即子节点具有空间位置属性，则该子节点对应的属性值为目标实体设备在车间中对应的空间位置；又例如，子节点为第二类节点，即子节点具有逻辑功能属性，则该子节点对应的属性值为目标实体设备在产线/工艺上对应的流程环节。关于对虚拟管理树中的子节点执行设备关联操作的可选方式可参见上述对子节点执行其他操作的方式，在此不做赘述。
在本申请实施例中，在将目标实体设备的标识添加至子节点的设备资产列表中时，可以根据目标实体设备的标识，判断目标实体设备是否具有与子节点适配的属性，并在判断不具有的情况下，输出提示信息，以供用户确认是否建立子节点与目标实体设备之间的关联关系。可选地，可以通过弹窗或浮层的方式输出提示信息，提示信息界面上包括用于执行确认操作与取消操作的控件，以供确定是否建立子节点与目标实体设备之间的关联关系。若用户确定建立子节点与目标实体设备之间的关联关系，可以对确认控件执行触发操作，并向系统发送确认关联指令。进一步，在接收到确认关联指令的情况下，可以建立子节点与目标实体设备之间的关联关系，并将目标实体设备的标识添加至子节点的设备资产列表中。若用户确定不建立子节点与目标实体设备之间的关联关系，可以对取消控件执行触发操作，向系统发送取消关联执行，则不建立子节点目标实体设备的关联关系。
在本申请实施例中，在根据目标实体设备标识判断目标实体设备是否具有与子节点适配的属性时，不限定获取目标实体设备属性的具体方式，可选地，可以根据目标实体设备的标识实时获取目标实体设备的属性信息，例如，实时向目标实体设备发送属性信息获取指令，以供目标实体设备返回对应的属性信息。在另一可选实施例中，还可以在将虚拟管理树中的子节点与目标实体设备进行关联时，提供属性信息输入功能，以供获取输入的属性信息。例如，在响应到用户执行关联触发操作的情况下，展 示设备关联界面，设备关联界面上还包括属性输入项，供用户输入目标设备的属性信息。进一步可选地，在确定目标实体设备不具有与子节点适配的属性时，若响应到用户对确认控件执行触发操作，还可以展示属性信息输入界面，以供用户输入目标实体设备的属性信息；进一步，在响应到用户在属性信息编辑界面上的输入操作的情况下，可以获取目标实体设备的属性信息，以及在响应到用户确定输入结束的情况下，建立目标实体设备与子节点的关联关系，并将目标实体设备的属性与子节点一并关联，以及将目标实体设备的标识添加到子节点对应的设备资产列表中。
在将虚拟管理树中的子节点与目标实体设备进行关联的情况下，即得到用于对实体设备进行管理的设备管理模型。进一步，在得到设备管理模型之后，还可以接收设备管理请求，该设备管理请求包括查询条件，查询条件包括待查询空间位置属性和待查询逻辑功能属性中的至少一种。基于此，在接收到设备管理请求的情况下，可以根据查询条件中的待查询空间位置属性和/或待查询逻辑功能属性，遍历设备管理模型中的至少一棵虚拟管理树，以得到符合查询条件的设备ID列表。进一步，可以根据设备ID列表获取指定实体空间中待管理实体设备的指标数据，以根据指标数据对待管理实体设备进行数据分析或管理。在本申请实施例中，不限定根据设备ID列表获取指定实体空间中待管理实体设备的指标数据的具体方式，可选地，可以根据设备ID列表中的设备ID向对应的实体设备发送指标数据获取请求，以供实体设备返回对应的指标数据；例如，可以向实体设备发动用于读取指标数据的SQL语句，以供实体设备执行该SQL语句读取并返回对应的指标数据。在另一可选实施例中，还可以预先根据各实体设备的指标数据进行训练，得到对实体设备对应的数据建模，在确定设备ID列表的情况下，可以根据设备ID列表中的各设备ID读取对应数据模型中的指标数据；其中，实体设备的指标数据包括但不限于实体设备的耗电量、停机次数、停机时长等等。基于此，在获取到待管理实体设备的指标数据的情况下，可以根据指标数据分析待管理实体设备的运行状态，以及在确定运行状态异常的情况下做出相应的处理。
在本申请实施例中，本申请实施例还提供有空间系统导出功能，如图1所示，空间系统页面上的功能控件还包括空间系统导出控件，用户在选中目标系统空间的情况下，可以触发空间系统导出控件，以将选中的目标系统空间及其中的虚拟管理树关联的多个实体设备的信息以及各实体设备之间的级联关系导出。由于在创建目标空间系统以及在目标空间系统中创建虚拟管理树时，会为每个目标系统空间创建唯一的系统标识(SystemCod)，以及为每棵虚拟管理树的根节点创建唯一的空间标识(SpaceCode)以及为每棵虚拟管理树中的所有子节点分别创建唯一的节点标识。基于此，在响应到 空间系统导出控件被触发的情况下，可以根据选中的目标系统空间对应的系统标识，查询与其对应的所有虚拟管理树的根节点对应的空间标识；进而根据每棵虚拟管理树中根节点与子节点的级联关系，查询每棵虚拟管理树中的所有子节点对应的节点标识；基于此，可以根据每个子节点与实体设备的关联关系，获取每个子节点关联的设备标识，以根据设备标识获取实体设备的相关信息。在本申请实施例中，不限定导出文件类型以及文件内容的具体形式，可选地，可以通过Excel表格的方式导出，在导出的Excel表格包括各层级的实体设备对应的标识；在另一可选实施例中，也可以通过文档的形式导出，在导出的文档中包括与虚拟管理树对应结构的树形图，图中每个节点为对应实体设备的标识。当然，上述导出的形式以及导出的内容仅为示例性说明，并不限于此，可选地，在导出的内容中还可以包括实体设备的名称、属性信息以及指标数据等等，具体可根据实际需求确定。
进一步可选地，在导出目标空间系统时，还可以选择按照不同维度导出目标空间系统的内容，以将目标空间系统中的全部内容或部分内容导出。图2e为按照不同维度导出目标空间系统的示意图，如图2e所示，用户在确定将目标空间系统导出之前，可以选择导出的类型，假设导出维度1为以工厂维度导出、导出维度2为以车间维度导出、导出维度3为以产线维度导出。基于此，用户可以按需选择任一导出维度将目标空间系统中对应的内容以Excel或者文档的形式导出。例如，用户选择以车间维度导出，则在触发确定控件的情况下，可以将目标系统中对应每个车间的内容以Excel或者文档的形式导出，当然，在实际应用中并不限于此，还可以实现不同的导出维度，具体可根据实际需求确定。
除了空间系统导出功能，本申请实施例还提供有空间系统导入功能，如图2a所示，空间系统页面上的功能控件还包括空间系统导入控件，用户可以通过触发空间系统导入控件，将预存有目标空间系统内容的文件导入到边缘计算设备中，并在将文件导入到边缘计算设备的情况下，在服务页面中创建对应的目标空间系统，以及在目标空间系统中渲染文件中对应的虚拟管理树中。基于此，在响应到用户触发空间系统导入控件的情况下，可以显示文件导入窗口，用户可以通过文件导入窗口将已有的文件导入到边缘计算设备中；边缘计算设备在获得到导入的文件的情况下，可以读取文件中的内容，并根据文件中的内容在服务页面中创建对应的目标空间系统，以及在目标空间系统中渲染对应的虚拟管理树，以供用户通过该虚拟管理树对其关联的设备进行管理。
基于上述，本申请实施例还提供一种设备管理方法，以通过上述实施例中的设备管理模型从多维度获取实体设备的指标数据，以对实体设备进行数据分析和管理。图3a为本申 请实施例提供的设备管理方法的流程图，如图3a所示，方法包括：
P1、接收设备管理请求，设备管理请求包括查询条件，查询条件包括待查询空间位置属性和待查询逻辑功能属性中的至少一种；
P2、遍历设备管理模型中的至少一棵虚拟管理树，以得到符合查询条件的设备ID列表，设备管理模型对应指定实体空间；
P3、根据设备ID列表获取指定实体空间中待管理实体设备的指标数据，根据指标数据对待管理实体设备进行数据分析或管理；
其中，至少一棵虚拟管理树至少包括具有空间位置属性的第一类节点和具有逻辑功能属性的第二类节点，不同空间位置属性对应指定实体空间中的不同空间位置，不同逻辑功能属性对应指定实体空间中存在的作业流程中的不同流程环节；设备管理模型是至少一棵虚拟管理树上的节点与指定实体空间中多个实体设备进行关联得到的。
在本申请实施例中，不限定获取设备管理模型的方式，可选地，可以通过上述设备管理模型生成方法中的方式获取设备管理模型。基于此，如图3b所示，在本申请实施例中，在步骤P1之前，还包括：
P01、响应于空间系统的创建操作，创建目标空间系统，目标空间系统对应于指定实体空间，指定实体空间包括多个实体设备；
P02、响应于管理模型的生成操作，在目标空间系统中生成至少一棵虚拟管理树，至少一棵虚拟管理树至少包括具有空间位置属性的第一类节点和具有逻辑功能属性的第二类节点，不同空间位置属性对应指定实体空间中的不同空间位置，不同逻辑功能属性对应指定实体空间中存在的作业流程中的不同流程环节；
P03、结合多个实体设备的空间位置属性和逻辑功能属性，将多个实体设备与至少一棵虚拟管理树上的节点进行关联，以得到多维度的设备管理模型。
需要说明的是，关于设备管理模型生成方法是具体过程以及如何通过设备管理模型对设备进行管理的过程可参见上述方法实施例的内容，在此不说赘述。上述实施例所提供方法的各步骤的执行主体均可以是同一设备，或者，该方法也由不同设备作为执行主体。比如，步骤S1至步骤S3、步骤P1至步骤P3的执行主体可以为设备A；又比如，步骤S1、步骤P1和步骤P2的执行主体可以为设备A，步骤S2和至步骤S3、步骤P4的执行主体可以为设备B；等等。
另外，在上述实施例及附图中的描述的一些流程中，包含了按照特定顺序出现的多个操作，但是应该清楚了解，这些操作可以不按照其在本文中出现的顺序来执行或并行执行，操作的序号如S1、P1等，仅仅是用于区分开各个不同的操作，序号本身不代表任何的执行顺序。另外，这些流程可以包括更多或更少的操作，并且这些操作可以按顺序执行或并行执行。需要说明的是，本文中的“第一”、“第二”等描述，是用于区分不同的消息、设 备、模块等，不代表先后顺序，也不限定“第一”和“第二”是不同的类型。
本申请实施例还提供一种设备管理模型生成装置，图4为本申请实施例提供的设备管理模型生成装置的结构示意图，如图4所示，设备管理模型生成装置包括创建模块401、第一生成模块402和第二生成模块403；其中，创建模块401用于响应于空间系统的创建操作，以创建目标空间系统，目标空间系统对应于指定实体空间，指定实体空间包括多个实体设备；第一生成模块402用于响应于管理模型的生成操作，在目标空间系统中生成至少一棵虚拟管理树，至少一棵虚拟管理树至少包括具有空间位置属性的第一类节点和具有逻辑功能属性的第二类节点，不同空间位置属性对应指定实体空间中的不同空间位置，不同逻辑功能属性对应指定实体空间中存在的作业流程中的不同流程环节；第二生成模块403用于结合多个实体设备的空间位置属性和逻辑功能属性，将多个实体设备与至少一棵虚拟管理树上的节点进行关联，以得到多维度的设备管理模型。
本申请实施例还提供一种设备管理装置，图5为本申请实施例提供的设备管理装置的结构示意图，如图5所示，设备管理装置包括接收模块501、查询模块502和管理模块503；其中，接收模块501用于接收设备管理请求，设备管理请求包括查询条件，查询条件包括待查询空间位置属性和待查询逻辑功能属性中的至少一种；查询模块502用于遍历设备管理模型中的至少一棵虚拟管理树，以得到符合查询条件的设备ID列表，设备管理模型对应指定实体空间；管理模块503用于根据设备ID列表获取指定实体空间中待管理实体设备的指标数据，以根据指标数据对待管理实体设备进行数据分析或管理；其中，至少一棵虚拟管理树至少包括具有空间位置属性的第一类节点和具有逻辑功能属性的第二类节点，不同空间位置属性对应指定实体空间中的不同空间位置，不同逻辑功能属性对应指定实体空间中存在的作业流程中的不同流程环节；设备管理模型是至少一棵虚拟管理树上的节点与指定实体空间中多个实体设备进行关联得到的。
需要说明的是，关于本申请实施例提供的设备管理模型生成装置和设备管理装置中各模块的具体功能和实现细节可参见上述方法实施例中对应部分的说明，在此不再赘述。
本申请实施例还提供了一种边缘计算设备，图6为本申请实施例提供的边缘计算设备的结构示意图，如图6所示，边缘计算设备包括：处理器61以及存储有计算机程序的存储器62和显示器63。其中，处理器61和存储器62可以是一个或多个。
存储器62，主要用于存储计算机程序，这些计算机程序可被处理器执行，致使处理器 控制处理器61使用边缘计算设备实现相应功能、完成相应动作或任务。除了存储计算机程序之外，存储器还可被配置为存储其它各种数据以支持在处理器61使用边缘计算设备上的操作，这些数据的示例包括用于在处理器61使用边缘计算设备上操作的任何应用程序或方法的指令。
存储器62，可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
在本申请实施例中，并不限定处理器61的实现形态，例如可以是但不限于CPU、GPU或MCU等。处理器61可以看作是边缘计算设备的控制单元，可用于执行存储器62中存储的计算机程序，以控制边缘计算设备实现相应功能、完成相应动作或任务。值得说明的是，根据边缘计算设备实现形态以及所处于场景的不同，其所需实现的功能、完成的动作或任务会有所不同；相应地，存储器62中存储的计算机程序也会有所不同，而处理器61执行不同计算机程序可控制边缘计算设备实现不同的功能、完成不同的动作或任务。
在一些可选实施例中，如图6所示，边缘计算设备还可以包括：通信组件64和电源组件65等其它组件。图6中仅示意性给出部分组件，并不意味着边缘计算设备只包括图6所示组件，针对不同的应用需求，边缘计算设备还可以包括其他组件，具体可视边缘计算设备的产品形态而定。
在本申请实施例中，当处理器61执行存储器62中的计算机程序时，以用于：响应于空间系统的创建操作，创建目标空间系统，目标空间系统对应于指定实体空间，指定实体空间包括多个实体设备；响应于管理模型的生成操作，在目标空间系统中生成至少一棵虚拟管理树，至少一棵虚拟管理树至少包括具有空间位置属性的第一类节点和具有逻辑功能属性的第二类节点，不同空间位置属性对应指定实体空间中的不同空间位置，不同逻辑功能属性对应指定实体空间中存在的作业流程中的不同流程环节；结合多个实体设备的空间位置属性和逻辑功能属性，将多个实体设备与至少一棵虚拟管理树上的节点进行关联，以得到多维度的设备管理模型。
在一可选实施例中，处理器61在响应于空间系统的创建操作，创建目标空间系统时，用于：响应于空间系统的创建操作，显示空间系统页面，并在空间系统页面上创建至少一棵基础树，至少一棵基础树和空间系统页面形成目标空间系统。
在一可选实施例中，处理器61在响应于管理模型的生成操作，在目标空间系统中生成至少一棵虚拟管理树时，用于：响应于管理模型的生成操作，显示目标空间系统对应的空间系统页面，空间系统页面上包括至少一棵基础树，每棵基础树包括根节点和属性为空的至少一级子节点；响应于对任一棵基础树的编辑触发操作，对基础树进行编辑操作，以得到包含根节点和具有属性的至少一级子节点的虚拟管理树，每个子 节点具有一种空间位置属性或一种逻辑功能属性。
在一可选实施例中，处理器61在响应于对任一棵基础树的编辑触发操作，对基础树进行编辑操作，以得到对应的虚拟管理树时，用于：响应于对任一棵基础树的编辑触发操作，显示编辑界面，并将基础树渲染至编辑界面上以得到待编辑树，待编辑树中的子节点绑定有编辑操作对应的事件；响应于对待编辑树的编辑操作，获取编辑操作产生的最新子节点及其属性和层级关系，并根据最新子节点及其属性和层级关系，生成虚拟管理树。
在一可选实施例中，编辑操作包括增加子节点、设置子节点属性、删除子节点、调整子节点层级关系中的至少一种，则处理器61在响应于对待编辑树的编辑操作，获取编辑操作产生的最新子节点及其属性和层级关系时，用于：响应于针对待编辑树中任一子节点的属性设置操作，显示属性设置界面，响应属性设置界面上的输入操作，获取子节点的属性；或者响应于针对待编辑树中任一子节点的节点添加操作，在子节点下面添加下一级子节点，以及响应于对下一级子节点的属性设置操作，获取下一级子节点的属性；或者响应于针对待编辑树中任一子节点的删除操作，删除子节点及其属性，并在子节点具有下级子节点的情况下，将子节点的下级子节点及其属性删除；或者响应于针对待编辑树中任一子节点的拖拽操作，根据子节点被拖拽到的目标位置，确定子节点最新的父节点和/或子节点，并根据最新的父节点和/或子节点修改子节点的层级关系。
在一可选实施例中，在虚拟管理树为多棵的情况下，多棵虚拟管理树中包括第一类管理树和第二类管理树，第一类管理树是指所有子节点均为第一类节点的虚拟管理树，第二类管理树是指所有子节点均为第二类节点的虚拟管理树；在虚拟管理树为一棵的情况下，虚拟管理树为第三类管理树，第三类管理树是指同时包含第一类节点和第二类节点的虚拟管理树。
在一可选实施例中，对任一棵虚拟管理树，子节点之间的层级关系反映各层子节点具有的属性之间的层级关系或级联关系，且同一层子节点具有空间位置属性和逻辑功能属性中的一类或两类，且同一类属性具有一种或多种。
在一可选实施例中，处理器61在结合多个实体设备的空间位置属性和逻辑功能属性，将多个实体设备与至少一棵虚拟管理树上的节点进行关联，以得到多维度的设备管理模型时，用于：针对每一棵虚拟管理树上的每个子节点，响应于针对子节点的关联触发操作，显示子节点具有的属性和设备关联界面；响应于设备关联界面上的输入操作，获取需要与子节点关联的目标实体设备的标识，将目标实体设备的标识添加至子节点的设备资产列表中，目标实体设备具有与子节点适配的属性。
在一可选实施例中，处理器61在将目标实体设备的标识添加至子节点的设备资产列表中时，用于：根据目标实体设备的标识，判断目标实体设备是否具有与子节点适 配的属性；在不具有的情况下，输出提示信息，以供关联人员确认是否建立子节点与目标实体设备之间的关联关系；在接收到确认关联指令的情况下，将目标实体设备的标识添加至子节点的设备资产列表中。
在一可选实施例中，在得到设备管理模型之后，处理器61还用于：接收设备管理请求，设备管理请求包括查询条件，查询条件包括待查询空间位置属性和待查询逻辑功能属性中的至少一种；遍历设备管理模型中的至少一棵虚拟管理树，以得到符合查询条件的设备ID列表；根据设备ID列表获取指定实体空间中待管理实体设备的指标数据，根据指标数据对待管理实体设备进行数据分析或管理。
相应地，本申请实施例还提供一种存储有计算机程序的计算机可读存储介质，当计算机程序被处理器执行时，致使处理器实现上述方法实施例中的各步骤。
相应地，本申请实施例还提供一种计算机程序产品，包括计算机程序/指令，当计算机程序/指令被处理器执行时，致使处理器实现上述方法实施例中的各步骤。
上述实施例中的通信组件被配置为便于通信组件所在设备和其他设备之间有线或无线方式的通信。通信组件所在设备可以接入基于通信标准的无线网络，如WiFi，2G、3G、4G/LTE、5G等移动通信网络，或它们的组合。在一个示例性实施例中，通信组件经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
上述实施例中的显示器包括屏幕，其屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。
上述实施例中的电源组件，为电源组件所在设备的各种组件提供电力。电源组件可以包括电源管理系统，一个或多个电源，及其他与为电源组件所在设备生成、管理和分配电力相关联的组件。
上述实施例中的音频组件，可被配置为输出和/或输入音频信号。例如，音频组件包括一个麦克风(MIC)，当音频组件所在设备处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器或经由通信组件发送。在一些实施例中，音频组件还包括一个扬声器，用于输出音频信号。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实 施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (14)

  1. 一种设备管理模型生成方法，其特征在于，包括：
    响应于空间系统的创建操作，创建目标空间系统，所述目标空间系统对应于指定实体空间，所述指定实体空间包括多个实体设备；
    响应于管理模型的生成操作，在所述目标空间系统中生成至少一棵虚拟管理树，所述至少一棵虚拟管理树至少包括具有空间位置属性的第一类节点和具有逻辑功能属性的第二类节点，不同空间位置属性对应所述指定实体空间中的不同空间位置，不同逻辑功能属性对应所述指定实体空间中存在的作业流程中的不同流程环节；
    结合所述多个实体设备的空间位置属性和逻辑功能属性，将所述多个实体设备与所述至少一棵虚拟管理树上的节点进行关联，以得到多维度的设备管理模型。
  2. 根据权利要求1所述的方法，其特征在于，响应于空间系统的创建操作，创建目标空间系统，包括：
    响应于空间系统的创建操作，显示空间系统页面，并在所述空间系统页面上创建至少一棵基础树，所述至少一棵基础树和所述空间系统页面形成目标空间系统。
  3. 根据权利要求2所述的方法，其特征在于，响应于管理模型的生成操作，在所述目标空间系统中生成至少一棵虚拟管理树，包括：
    响应于管理模型的生成操作，显示所述目标空间系统对应的空间系统页面，所述空间系统页面上包括至少一棵基础树，每棵基础树包括根节点和属性为空的至少一级子节点；
    响应于对任一棵基础树的编辑触发操作，对所述基础树进行编辑操作，以得到包含根节点和具有属性的至少一级子节点的虚拟管理树，每个子节点具有一种空间位置属性或一种逻辑功能属性。
  4. 根据权利要求3所述的方法，其特征在于，响应于对任一棵基础树的编辑触发操作，对所述基础树进行编辑操作，以得到对应的虚拟管理树，包括：
    响应于对任一棵基础树的编辑触发操作，显示编辑界面，并将所述基础树渲染至所述编辑界面上以得到待编辑树，所述待编辑树中的子节点绑定有编辑操作对应的事件；
    响应于对所述待编辑树的编辑操作，获取所述编辑操作产生的最新子节点及其属性和层级关系，并根据所述最新子节点及其属性和层级关系，生成虚拟管理树。
  5. 根据权利要求4所述的方法，其特征在于，所述编辑操作包括增加子节点、设置子节点属性、删除子节点、调整子节点层级关系中的至少一种，则响应于对所述待编辑树的编辑操作，获取所述编辑操作产生的最新子节点及其属性和层级关系，包括：
    响应于针对所述待编辑树中任一子节点的属性设置操作，显示属性设置界面，响应所述属性设置界面上的输入操作，获取所述子节点的属性；
    或者
    响应于针对所述待编辑树中任一子节点的节点添加操作，在所述子节点下面添加下一级子节点，以及响应于对所述下一级子节点的属性设置操作，获取所述下一级子节点的属性；
    或者
    响应于针对所述待编辑树中任一子节点的删除操作，删除所述子节点及其属性，并在所述子节点具有下级子节点的情况下，将所述子节点的下级子节点及其属性删除；
    或者
    响应于针对所述待编辑树中任一子节点的拖拽操作，根据所述子节点被拖拽到的目标位置，确定所述子节点最新的父节点和/或子节点，并根据最新的父节点和/或子节点修改所述子节点的层级关系。
  6. 根据权利要求3-5任一项所述的方法，其特征在于，在所述虚拟管理树为多棵的情况下，多棵虚拟管理树中包括第一类管理树和第二类管理树，所述第一类管理树是指所有子节点均为第一类节点的虚拟管理树，所述第二类管理树是指所有子节点均为第二类节点的虚拟管理树；在所述虚拟管理树为一棵的情况下，所述虚拟管理树为第三类管理树，所述第三类管理树是指同时包含第一类节点和第二类节点的虚拟管理树。
  7. 根据权利要求6所述的方法，其特征在于，对任一棵虚拟管理树，子节点之间的层级关系反映各层子节点具有的属性之间的层级关系或级联关系，且同一层子节点具有空间位置属性和逻辑功能属性中的一类或两类，且同一类属性具有一种或多种。
  8. 根据权利要求1-5任一项所述的方法，其特征在于，结合所述多个实体设备的空间位置属性和逻辑功能属性，将所述多个实体设备与所述至少一棵虚拟管理树上的节点进行关联，以得到多维度的设备管理模型，包括：
    针对每一棵虚拟管理树上的每个子节点，响应于针对所述子节点的关联触发操作，显示所述子节点具有的属性和设备关联界面；
    响应于所述设备关联界面上的输入操作，获取需要与所述子节点关联的目标实体设备的标识，将所述目标实体设备的标识添加至所述子节点的设备资产列表中，所述目标实体设备具有与所述子节点适配的属性。
  9. 根据权利要求8所述的方法，其特征在于，将所述目标实体设备的标识添加至所述子节点的设备资产列表中，包括：
    根据所述目标实体设备的标识，判断所述目标实体设备是否具有与所述子节点适配的属性；
    在不具有的情况下，输出提示信息，以供关联人员确认是否建立所述子节点与所述目标实体设备之间的关联关系；
    在接收到确认关联指令的情况下，将所述目标实体设备的标识添加至所述子节点的设备资产列表中。
  10. 根据权利要求1-5任一项所述的方法，其特征在于，在得到所述设备管理模型之后，还包括：
    接收设备管理请求，所述设备管理请求包括查询条件，所述查询条件包括待查询空间位置属性和待查询逻辑功能属性中的至少一种；
    遍历所述设备管理模型中的至少一棵虚拟管理树，以得到符合所述查询条件的设备ID列表；
    根据所述设备ID列表获取所述指定实体空间中待管理实体设备的指标数据，根据所述指标数据对所述待管理实体设备进行数据分析或管理。
  11. 一种设备管理方法，其特征在于，包括：
    接收设备管理请求，所述设备管理请求包括查询条件，所述查询条件包括待查询空间位置属性和待查询逻辑功能属性中的至少一种；
    遍历设备管理模型中的至少一棵虚拟管理树，以得到符合所述查询条件的设备ID列表，所述设备管理模型对应指定实体空间；
    根据所述设备ID列表获取所述指定实体空间中待管理实体设备的指标数据，根据所述指标数据对所述待管理实体设备进行数据分析或管理；
    其中，所述至少一棵虚拟管理树至少包括具有空间位置属性的第一类节点和具有逻辑功能属性的第二类节点，不同空间位置属性对应所述指定实体空间中的不同空间位置，不同逻辑功能属性对应所述指定实体空间中存在的作业流程中的不同流程环节；所述设备管理模型是所述至少一棵虚拟管理树上的节点与所述指定实体空间中多个实体设备进行关联得到的。
  12. 一种设备管理模型生成装置，其特征在于，包括：
    创建模块，用于响应于空间系统的创建操作，以创建目标空间系统，所述目标空间系统对应于指定实体空间，所述指定实体空间包括多个实体设备；
    第一生成模块，用于响应于管理模型的生成操作，在所述目标空间系统中生成至少一棵虚拟管理树，所述至少一棵虚拟管理树至少包括具有空间位置属性的第一类节点和具有逻辑功能属性的第二类节点，不同空间位置属性对应所述指定实体空间中的不同空间位置，不同逻辑功能属性对应所述指定实体空间中存在的作业流程中的不同流程环节；
    第二生成模块，用于结合所述多个实体设备的空间位置属性和逻辑功能属性，将所述多个实体设备与所述至少一棵虚拟管理树上的节点进行关联，以得到多维度的设备管理模型。
  13. 一种边缘计算设备，其特征在于，包括：显示器、处理器以及存储有计算机程序的存储器，所述处理器用于执行所述计算机程序，以用于执行权利要求1-11任一项所述方法中的步骤。
  14. 一种存储有计算机程序的计算机可读存储介质，其特征在于，当所述计算机程序被处理器执行时，致使所述处理器实现权利要求1-11任一项所述方法中的步骤。
PCT/CN2023/082342 2022-03-24 2023-03-17 设备管理模型生成与设备管理方法、设备及存储介质 WO2023179504A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210303417.X 2022-03-24
CN202210303417.XA CN114693103A (zh) 2022-03-24 2022-03-24 设备管理模型生成与设备管理方法、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023179504A1 true WO2023179504A1 (zh) 2023-09-28

Family

ID=82138821

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/082342 WO2023179504A1 (zh) 2022-03-24 2023-03-17 设备管理模型生成与设备管理方法、设备及存储介质

Country Status (2)

Country Link
CN (1) CN114693103A (zh)
WO (1) WO2023179504A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114693103A (zh) * 2022-03-24 2022-07-01 阿里云计算有限公司 设备管理模型生成与设备管理方法、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111107131A (zh) * 2019-11-05 2020-05-05 远景智能国际私人投资有限公司 物联网设备的管理方法、装置、服务器及存储介质
US20200410044A1 (en) * 2019-06-28 2020-12-31 Baidu Online Network Technology (Beijing) Co., Ltd. Visualized edition method, device and apparatus, and storage medium
CN112231917A (zh) * 2020-10-20 2021-01-15 深圳市万物云科技有限公司 空间数字孪生建模方法、装置、计算机设备及存储介质
CN113255170A (zh) * 2021-07-06 2021-08-13 江苏中车数字科技有限公司 一种云边协同工厂数字孪生监控建模系统和建模方法
CN114693103A (zh) * 2022-03-24 2022-07-01 阿里云计算有限公司 设备管理模型生成与设备管理方法、设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200410044A1 (en) * 2019-06-28 2020-12-31 Baidu Online Network Technology (Beijing) Co., Ltd. Visualized edition method, device and apparatus, and storage medium
CN111107131A (zh) * 2019-11-05 2020-05-05 远景智能国际私人投资有限公司 物联网设备的管理方法、装置、服务器及存储介质
CN112231917A (zh) * 2020-10-20 2021-01-15 深圳市万物云科技有限公司 空间数字孪生建模方法、装置、计算机设备及存储介质
CN113255170A (zh) * 2021-07-06 2021-08-13 江苏中车数字科技有限公司 一种云边协同工厂数字孪生监控建模系统和建模方法
CN114693103A (zh) * 2022-03-24 2022-07-01 阿里云计算有限公司 设备管理模型生成与设备管理方法、设备及存储介质

Also Published As

Publication number Publication date
CN114693103A (zh) 2022-07-01

Similar Documents

Publication Publication Date Title
US11902313B2 (en) Dynamic hierarchical tagging system and method
US20230359595A1 (en) Managing and classifying assets in an information technology environment using tags
US9436347B2 (en) Methods and systems for entering object assignments
US8838667B2 (en) Event routing mechanism in a computer system
US20210125144A1 (en) Bill of material conversion method, electronic apparatus and non-transitory computer-readable storage medium
US20200065313A1 (en) Extensible content object metadata
CN110119393B (zh) 代码版本管理系统及方法
WO2006059240A2 (en) User interface for complex process inplementation
WO2018036342A1 (zh) 基于csar的模型文件的可视化设计方法及装置
WO2023179504A1 (zh) 设备管理模型生成与设备管理方法、设备及存储介质
CN111949832A (zh) 批量作业依赖关系的解析方法及装置
CN112433712A (zh) 报表展示方法、装置、计算机设备和存储介质
CN111427865A (zh) 一种管理数据库的对象的方法和装置
CN110532058B (zh) 容器集群服务的管理方法、装置、设备及可读存储介质
CN110941629A (zh) 元数据处理方法、装置、设备及计算机可读存储介质
CN112785248B (zh) 人力资源数据跨组织交互方法、装置、设备和存储介质
CN103440300B (zh) 基于事件对文件进行管理的操作系统的工作方法
CN113515275A (zh) 一种所见即所得的云端工业组态软件系统及其开发方法
CN112199200A (zh) 资源调度方法、装置、计算机设备和存储介质
JP5916897B2 (ja) プロジェクトデータ作成装置
CN115169891A (zh) 一种包含多起点多分支流程的工作流引擎
CN114895875A (zh) 一种零代码可视化信息系统元数据的生产应用方法及系统
JP5884925B2 (ja) 管理支援装置、管理支援方法及び管理支援プログラム
KR101949727B1 (ko) 객체간 링크 생성 시스템 및 이의 동작 방법
JP5682452B2 (ja) 変更管理支援装置、変更管理支援方法及び変更管理支援プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23773752

Country of ref document: EP

Kind code of ref document: A1