CN116976086A - System data processing method, device, equipment and medium - Google Patents
System data processing method, device, equipment and medium Download PDFInfo
- Publication number
- CN116976086A CN116976086A CN202310757732.4A CN202310757732A CN116976086A CN 116976086 A CN116976086 A CN 116976086A CN 202310757732 A CN202310757732 A CN 202310757732A CN 116976086 A CN116976086 A CN 116976086A
- Authority
- CN
- China
- Prior art keywords
- sensor
- entity
- node
- equipment
- attribute
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 14
- 238000005094 computer simulation Methods 0.000 claims abstract description 196
- 238000012545 processing Methods 0.000 claims abstract description 132
- 238000000034 method Methods 0.000 claims abstract description 121
- 238000005259 measurement Methods 0.000 claims description 565
- 238000003860 storage Methods 0.000 claims description 187
- 238000013507 mapping Methods 0.000 claims description 161
- 238000001514 detection method Methods 0.000 claims description 102
- 230000005856 abnormality Effects 0.000 claims description 58
- 238000013500 data storage Methods 0.000 claims description 42
- 230000002159 abnormal effect Effects 0.000 claims description 41
- 238000004590 computer program Methods 0.000 claims description 17
- 238000001816 cooling Methods 0.000 description 161
- 238000005057 refrigeration Methods 0.000 description 119
- 239000011449 brick Substances 0.000 description 94
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 85
- 238000010586 diagram Methods 0.000 description 37
- 230000008569 process Effects 0.000 description 35
- 238000013473 artificial intelligence Methods 0.000 description 27
- 238000005516 engineering process Methods 0.000 description 26
- 238000007710 freezing Methods 0.000 description 21
- 230000008014 freezing Effects 0.000 description 21
- 238000004422 calculation algorithm Methods 0.000 description 18
- 238000004891 communication Methods 0.000 description 18
- 238000013479 data entry Methods 0.000 description 11
- 238000004088 simulation Methods 0.000 description 11
- 238000010276 construction Methods 0.000 description 10
- 238000005265 energy consumption Methods 0.000 description 10
- 238000010438 heat treatment Methods 0.000 description 9
- 238000009423 ventilation Methods 0.000 description 9
- 238000004378 air conditioning Methods 0.000 description 8
- 238000012549 training Methods 0.000 description 8
- 230000009286 beneficial effect Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 238000004458 analytical method Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 5
- 238000010801 machine learning Methods 0.000 description 5
- 239000000498 cooling water Substances 0.000 description 4
- 238000013499 data model Methods 0.000 description 4
- 238000013461 design Methods 0.000 description 4
- 230000010354 integration Effects 0.000 description 4
- 238000007726 management method Methods 0.000 description 4
- 241000196324 Embryophyta Species 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 3
- 238000009826 distribution Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000005457 optimization Methods 0.000 description 3
- 239000003507 refrigerant Substances 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 238000011144 upstream manufacturing Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000007405 data analysis Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000004134 energy conservation Methods 0.000 description 2
- 230000007613 environmental effect Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 230000001105 regulatory effect Effects 0.000 description 2
- 238000012384 transportation and delivery Methods 0.000 description 2
- 208000025174 PANDAS Diseases 0.000 description 1
- 208000021155 Paediatric autoimmune neuropsychiatric disorders associated with streptococcal infection Diseases 0.000 description 1
- 240000000220 Panda oleosa Species 0.000 description 1
- 235000016496 Panda oleosa Nutrition 0.000 description 1
- 230000002547 anomalous effect Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000013528 artificial neural network Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000033228 biological regulation Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 239000000306 component Substances 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 239000008358 core component Substances 0.000 description 1
- 238000007728 cost analysis Methods 0.000 description 1
- 238000013135 deep learning Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000005611 electricity Effects 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000008020 evaporation Effects 0.000 description 1
- 238000001704 evaporation Methods 0.000 description 1
- 230000006698 induction Effects 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 238000000053 physical method Methods 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 238000013441 quality evaluation Methods 0.000 description 1
- 230000002787 reinforcement Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000007619 statistical method Methods 0.000 description 1
- 238000013526 transfer learning Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F30/00—Computer-aided design [CAD]
- G06F30/20—Design optimisation, verification or simulation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
- G06F16/90335—Query processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/907—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Geometry (AREA)
- Evolutionary Computation (AREA)
- Library & Information Science (AREA)
- Computer Hardware Design (AREA)
- Computational Linguistics (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application provides a system data processing method, a device, equipment and a medium, wherein the method comprises the following steps: acquiring service metadata for performing system modeling from a service data table, when equipment metadata of service equipment exists in the service metadata, establishing equipment instances of the service equipment based on the equipment metadata, when sensor metadata of equipment sensors deployed on the service equipment exists in the service metadata, establishing sensor instances of the equipment sensors based on the sensor metadata, configuring equipment nodes in the equipment instances as equipment master nodes based on equipment subordination between the service equipment and the equipment sensors, configuring the sensor nodes in the sensor instances as equipment child nodes subordinate to the equipment master nodes, and obtaining a system modeling model of the service processing system based on the equipment nodes, the equipment master nodes, the sensor nodes and the equipment child nodes. The application can improve the modeling efficiency of the system aiming at the service processing system.
Description
Technical Field
The present application relates to the field of computer processing technologies, and in particular, to a system data processing method, apparatus, device, and medium.
Background
Currently, business systems (such as refrigeration systems in data center systems) can be systematically modeled for use in the construction of simulation systems, and the like. For example, the modeling can be performed on equipment deployed in a service system and sensors deployed in the equipment, and the simulation system is constructed through a model obtained through modeling. In the prior art, when modeling a system for a service system, a modeler needs to manually write connection relations between various devices (such as a device and a sensor deployed on the device) in the service system in sequence. When a large number of sensors are deployed on the equipment related to one service system, the relation between the equipment and the sensors is complicated, which increases the complexity and difficulty of the whole system modeling process during manual modeling, and in addition, because the manual modeling process is complicated and tedious and is easy to make mistakes, a long manual modeling time is required to be consumed for system modeling to ensure the accuracy of the manual modeling, so that the efficiency of system modeling is reduced.
Disclosure of Invention
The embodiment of the application provides a system data processing method, device, equipment and medium, which can optimize the system modeling process of a service processing system, thereby improving the system modeling efficiency.
In one aspect, an embodiment of the present application provides a system data processing method, where the method includes:
acquiring service metadata for system modeling from a service data table associated with a service processing system; the service processing system comprises service equipment deployed in a physical space; deploying a device sensor on the service device;
when equipment type metadata of the service equipment exists in the service metadata, establishing an equipment instance of the service equipment based on the equipment type metadata; the equipment instance is used for recording equipment class nodes and equipment nodes of the service equipment; the device node is subordinate to the device class node;
when the sensor class metadata of the device sensors deployed on the service device exist in the service metadata, establishing a sensor instance of the device sensors based on the sensor class metadata; the sensor instance is used for recording sensor class nodes and sensor nodes of the equipment sensor; the sensor node is subordinate to the sensor class node;
based on the device subordinate relation between the service device and the device sensor, configuring the device node in the device instance as a device master node, and configuring the sensor node in the sensor instance as a device child node subordinate to the device master node;
Based on the equipment class node, the equipment main node, the sensor class node and the equipment sub-node, modeling to obtain a system modeling model of the service processing system; the system modeling model is used to query device dependencies between business devices and device sensors.
In one aspect, an embodiment of the present application provides a system data processing apparatus, including:
the business metadata acquisition module is used for acquiring business metadata for system modeling from a business data table associated with the business processing system; the service processing system comprises service equipment deployed in a physical space; the service equipment is provided with an equipment sensor;
the device instance establishing module is used for establishing a device instance of the service device based on the device metadata when the device metadata of the service device exists in the service metadata; the equipment instance is used for recording equipment class nodes and equipment nodes of the service equipment; the device node is subordinate to the device class node;
the sensor instance establishing module is used for establishing a sensor instance of the equipment sensor based on the sensor class metadata when the sensor class metadata of the equipment sensor deployed on the business equipment exists in the business metadata; the sensor instance is used for recording sensor class nodes and sensor nodes of the equipment sensor; the sensor node is subordinate to the sensor class node;
The node configuration module is used for configuring the equipment nodes in the equipment instance as equipment master nodes and configuring the sensor nodes in the sensor instance as equipment child nodes subordinate to the equipment master nodes based on the equipment subordinate relation between the service equipment and the equipment sensors;
the system modeling module is used for modeling based on the equipment class node, the equipment main node, the sensor class node and the equipment sub-node to obtain a system modeling model of the service processing system; the system modeling model is used to query device dependencies between business devices and device sensors.
An aspect of an embodiment of the present application provides a computer device, including a memory and a processor, where the memory is connected to the processor, and the memory is used to store a computer program, and the processor is used to call the computer program, so that the computer device performs the method provided in the foregoing aspect of the embodiment of the present application.
An aspect of an embodiment of the present application provides a computer readable storage medium, in which a computer program is stored, the computer program being adapted to be loaded and executed by a processor, to cause a computer device having a processor to perform the method provided in the above aspect of an embodiment of the present application.
According to one aspect of the present application, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the method provided in the above aspect.
In the embodiment of the application, the service metadata for carrying out system modeling can be acquired from the service data table associated with the service processing system, and when the equipment type metadata of the service equipment exists in the service metadata, the equipment instance of the service equipment is established based on the equipment type metadata, and the equipment instance is used for recording the equipment type nodes of the service equipment in the service processing system and the equipment nodes subordinate to the equipment type nodes; the device instance can be automatically constructed based on the device metadata, so that the service device is mapped from a physical space to a modeling mapping space, namely, the service device which is actually present is subjected to data structuring, so that the datamation entity device corresponding to the service device is obtained, and the data space (digital space) where the entity device is located is the modeling mapping space; similarly, when the sensor class metadata of the device sensors deployed on the service equipment exist in the service metadata, a sensor instance of the device sensors is established based on the sensor class metadata, wherein the sensor instance is used for recording sensor class nodes of the device sensors in the service equipment and sensor nodes subordinate to the sensor class nodes; in this way, the automatic construction of the sensor instance can be performed based on the sensor metadata so as to map the equipment sensor from the physical space to the modeling mapping space, namely, the data structure of the equipment sensor which exists truly is realized so as to obtain the entity sensor which corresponds to the equipment sensor and has the data; in addition, the device node in the device instance can be configured as a device master node based on the device subordinate relation (such as recorded in a service data table) between the service device and the device sensor, and the sensor node in the sensor instance is configured as a device child node subordinate to the device master node, so that the association between the entity device and the entity sensor is automatically performed in the modeling mapping space, and the service device, the device sensor and the device subordinate relation between the service device and the device sensor in the service processing system can be digitally represented based on the system modeling model obtained by modeling the device class node, the device master node, the sensor class node and the device child node; it can be understood that a modeler can realize system modeling of the service processing system only by providing the service data table without performing a great deal of complicated operations, so that the system modeling process of the service processing system can be optimized, the complexity and difficulty of the whole system modeling process are reduced, and the system modeling efficiency and modeling convenience for the service processing system are further improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram of a network architecture according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a system modeling process provided by an embodiment of the present application;
FIG. 3 is a flowchart illustrating a system data processing method according to an embodiment of the present application;
FIG. 4 is a schematic diagram of an establishment procedure of an example device according to an embodiment of the present application;
fig. 5 is a schematic diagram of a setup scenario of an embodiment of a device provided in the present application;
fig. 6 is a second schematic diagram of an establishment scenario of an embodiment of the present application;
FIG. 7 is a schematic diagram of a scenario for creating a system modeling model according to an embodiment of the present application;
FIG. 8 is a second schematic diagram of a system modeling model according to an embodiment of the present application;
FIG. 9 is a second flowchart of a system data processing method according to an embodiment of the present application;
FIG. 10 is a schematic diagram of a process for establishing an example of a sensor according to an embodiment of the present application;
FIG. 11 is a schematic diagram of an exemplary sensor setup scenario provided by an embodiment of the present application;
FIG. 12 is a schematic diagram of a system modeling model establishment process according to an embodiment of the present application;
FIG. 13 is a schematic diagram II of a system modeling model establishment process according to an embodiment of the present application;
FIG. 14 is a schematic diagram of an application scenario of system modeling according to an embodiment of the present application;
fig. 15 is a second schematic diagram of an application scenario of system modeling according to an embodiment of the present application;
fig. 16 is a third application scenario diagram of system modeling according to an embodiment of the present application;
fig. 17 is a schematic diagram of an application scenario of system modeling according to an embodiment of the present application;
fig. 18 is a schematic diagram of an application scenario of system modeling according to an embodiment of the present application;
fig. 19 is a schematic diagram of an application scenario of system modeling according to an embodiment of the present application;
fig. 20 is a schematic diagram seventh of an application scenario of system modeling according to an embodiment of the present application;
FIG. 21 is a schematic diagram eight of an application scenario of system modeling according to an embodiment of the present application;
FIG. 22 is a schematic diagram of a data set construction scenario provided by an embodiment of the present application;
FIG. 23 is a schematic diagram of a system data processing device according to an embodiment of the present application;
fig. 24 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Referring to fig. 1, fig. 1 is a schematic diagram of a network architecture according to an embodiment of the present application. As shown in fig. 1, the system architecture may include a service server 100 and a service terminal cluster, where the service terminal cluster may include one or more service terminals (e.g., user terminals), and the number of service terminals in the service terminal cluster will not be limited herein. As shown in fig. 1, the plurality of service terminals in the service terminal cluster may specifically include: the service terminals 200a, 200b, …, and 200n, wherein a communication connection may exist between the service terminal clusters, for example, a communication connection exists between the service terminal 200a and the service terminal 200b, and a communication connection exists between the service terminal 200a and the service terminal 200 n. Meanwhile, any service terminal in the service terminal cluster may have a communication connection with the service server 100, so that each service terminal in the service terminal cluster may perform data interaction with the service server 100 through the communication connection, for example, a communication connection exists between the service terminal 200a and the service server 100. The communication connection is not limited to a connection manner, and may be directly or indirectly connected through a wired communication manner, may be directly or indirectly connected through a wireless communication manner, or may be other manners, and the present application is not limited herein.
It should be understood that each service terminal in the service terminal cluster as shown in fig. 1 may be installed with an application client for system modeling. When the application client runs in each service terminal, data interaction can be performed between the application client and the service server 100 shown in fig. 1. The application client may be any type of client, such as a social client, an image processing client, an instant messaging client (e.g., a conference client), an entertainment client (e.g., a game client, a live broadcast client), a multimedia client (e.g., a video client), an information client (e.g., a news information client), a shopping client, a vehicle client, a modeling client, and the like, which have a function of displaying data information such as text, image, audio, and video.
For example, the data interaction process between the service terminal 200a and the service server 100 will be described herein by taking an application client as an example of a modeling client. The modeling client is a client capable of immediately transmitting and receiving internet messages and having an information searching function and the like, and a modeling module may be configured in the service server. The service terminal 200a may transmit a service data table for system modeling to the service server, and the service server may call the modeling module to perform system modeling of the service processing system through the service data table, and may return a model obtained after the system modeling to the service terminal 200a.
Optionally, it may be understood that the modeling module according to the embodiment of the present application may be integrated in whole or in part on a service terminal, where the service terminal directly implements system modeling of the service processing system through the modeling module.
It may be understood that the computer device according to the embodiment of the present application may be a server (for example, the service server 100 shown in fig. 1) or a terminal (for example, any service terminal in the service terminal cluster shown in fig. 1). The server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs (Content Delivery Network, content delivery networks), basic cloud computing services such as big data and artificial intelligent platforms, and the like. The terminal may be, but is not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, a vehicle-mounted terminal, etc.
It should be understood that fig. 1 is merely an exemplary representation of a possible network architecture according to the present application, and is not limited to a specific architecture according to the present application, i.e. the present application may also provide other network architectures.
It can be appreciated that the present application provides a system modeling method for a business processing system. A service device and a data collector disposed in the service device may be included in the service processing system, where the data collector may be configured to collect data associated with the service device, e.g., where the data collector is a temperature collector (temperature sensor), and may be configured to collect temperature data. The system modeling process can be as follows: acquiring service metadata for system modeling from a service data table associated with a service processing system; when equipment type metadata of the service equipment exists in the service metadata, establishing an equipment instance of the service equipment based on the equipment type metadata; the equipment instance is used for recording equipment class nodes and equipment nodes of the service equipment; the device node is subordinate to the device class node; when collector class metadata of a data collector deployed on service equipment exists in the service metadata, a collector instance of the data collector is established based on the collector class metadata; the collector instance is used for recording collector class nodes and collector nodes of the data collector; collector nodes are subordinate to collector class nodes; based on the equipment subordinate relation between the service equipment and the data collector, configuring equipment nodes in the equipment instance as equipment main nodes, and configuring collector nodes in the collector instance as equipment sub-nodes subordinate to the equipment main nodes; based on the equipment class node, the equipment main node, the collector class node and the equipment sub-node, modeling to obtain a system modeling model of the service processing system; the system modeling model is used for inquiring the device dependency relationship between the service device and the data collector. Such as which data collector belongs to which service device.
It can be understood that the application can be applied to system modeling of a business system in which business devices are arbitrarily deployed and in which data collectors are deployed. For example, the service processing system to be modeled may be a refrigeration system (such as refrigeration equipment including a refrigeration host, a refrigeration pump, a cooling tower, and the like) in a data center system, where the data collector may be an equipment sensor (such as a temperature sensor) in the refrigeration equipment, for measuring a collection temperature, where the collector metadata may be sensor metadata, and the collector instance may be a sensor instance, where the collector nodes and the collector nodes in the collector instance are sensor nodes and sensor nodes), or a device (such as a scanning device, for scanning a collection frame, where the collector metadata may be device metadata, and the collector instance may be a device instance, where the collector nodes and the collector nodes in the collector instance are device nodes and device nodes), and the equipment sensor is an example. For example, the refrigeration system comprises a refrigeration host and a refrigeration pump, wherein a power sensor can be arranged in the refrigeration host, and an operation state sensor can be arranged in the refrigeration pump; the device instance of the refrigeration host can be established through the device metadata of the refrigeration host, the device instance of the cooling pump is established through the device metadata of the cooling pump, the sensor instance of the power sensor is established through the sensor metadata of the power sensor, the sensor instance of the running state sensor is established through the sensor metadata of the running state sensor, meanwhile, the association between the device instance of the refrigeration host and the sensor instance of the power sensor can be carried out based on the device dependency between the refrigeration host and the power sensor, the association between the device instance of the refrigeration pump and the sensor instance of the running state sensor is carried out based on the device dependency between the refrigeration pump and the running state sensor, so that a system modeling model of the refrigeration system is obtained through modeling, and at the moment, the system modeling model can be used for inquiring the device dependency between the refrigeration system and the power sensor and the device dependency between the refrigeration pump and the running state sensor. Further, if it is determined that the device connection relationship exists between the refrigeration host and the cryopump according to the architecture of the refrigeration system, the device instance of the refrigeration host and the device instance of the cryopump may be associated to update the system modeling model, so that the updated system modeling model may be further used to query that the device connection relationship exists between the refrigeration host and the cryopump. That is, the modeled system modeling model may be used to record the relationship between the business devices and the device sensors in the refrigeration system (optionally, the relationship between the business devices may also be recorded).
For another example, the service processing system to be modeled may be a security system (such as a security device including a camera, an intelligent access control, an alarm, etc.) in an intelligent building system, where the data collector may be a device sensor (such as a temperature sensor) in the security device, for measuring a collection temperature, where the collector metadata may be sensor metadata, a collector instance may be a sensor instance, where the collector nodes and the collector nodes in the collector instance may be sensor nodes and sensor nodes), or a device (such as a scanning device, for scanning a collection frame, where the collector metadata may be device metadata, the collector instance may be a device instance, and the collector nodes in the collector instance may be device nodes and device nodes), taking the device sensor as an example. For example, the safety device comprises an intelligent access control and a camera, wherein a temperature sensor can be arranged in the intelligent access control, and an infrared sensor can be arranged in the camera; the device instance of the intelligent access control can be established through the device metadata of the intelligent access control, the device instance of the camera is established through the device metadata of the camera, the sensor instance of the temperature sensor is established through the sensor metadata of the temperature sensor, the sensor instance of the infrared sensor is established through the sensor metadata of the infrared sensor, meanwhile, the association between the device instance of the intelligent access control and the sensor instance of the temperature sensor can be carried out based on the device dependency relationship between the intelligent access control and the temperature sensor, the association between the device instance of the camera and the sensor instance of the infrared sensor is carried out based on the device dependency relationship between the camera and the infrared sensor, so that a system modeling model of the safety system is obtained through modeling, and at the moment, the system modeling model can be used for inquiring the device dependency relationship between the intelligent access control and the temperature sensor and the device dependency relationship between the camera and the infrared sensor. Furthermore, if the device connection relationship exists between the intelligent access control and the camera according to the architecture of the security system, the device instance of the intelligent access control and the device instance of the camera can be associated to update the system modeling model, so that the updated system modeling model can be used for inquiring the device connection relationship between the intelligent access control and the camera. That is, the modeled system modeling model may be used to record the relationship between business devices and device sensors in a security system (optionally, the relationship between business devices may also be recorded). The business processing system that performs the system modeling is not limited herein. The following describes the technical scheme of the application by taking a service processing system as a refrigerating system as an example.
Further, referring to fig. 2, fig. 2 is a schematic diagram illustrating a system modeling process according to an embodiment of the present application. The computer device 20 shown in fig. 2 may be any service terminal (e.g., the service terminal 200 a) in the service server 100 or the service terminal cluster in the embodiment corresponding to fig. 1, which is not limited herein, and the computer device 20 is taken as an example of the service server. Wherein the computer device 20 obtains a service data table 21 associated with a service processing system, and obtains service metadata 22 for performing system modeling from the service data table, wherein the service processing system refers to a system (such as a refrigeration system) actually existing in a physical space, the service processing system can be deployed with service devices, the service devices refer to devices (such as refrigeration hosts in the refrigeration system) actually existing in the physical space, and the service devices are deployed with device sensors, the device sensors refer to sensors (such as temperature sensors in the refrigeration hosts) actually existing in the physical space; when the equipment type metadata 23 of the service equipment exists in the service metadata, an equipment instance 24 of the service equipment is established based on the equipment metadata, wherein the equipment instance is used for recording equipment type nodes 25 and equipment nodes 26 of the service equipment in a modeling mapping space corresponding to a physical space, and the equipment nodes are subordinate to the equipment type nodes (namely, the equipment nodes point to the equipment type nodes in the modeling mapping space); accordingly, when the sensor class metadata 27 of the device sensor deployed on the service device exists in the service metadata, a sensor instance 28 of the device sensor is established based on the sensor class metadata, where the sensor instance is used for recording a sensor class node 29 and a sensor node 210 of the device sensor in a modeling mapping space corresponding to the physical space, and the sensor node is subordinate to the sensor class node (i.e., the sensor node points to the sensor class node in the modeling mapping space); meanwhile, based on the device subordinate relation between the service device and the device sensor, configuring the device node in the device instance as a device master node, configuring the sensor node in the sensor instance as a device child node subordinate to the device master node (namely, the sensor node points to the device node in the modeling mapping space), namely, based on the device subordinate relation between the service device and the device sensor, establishing the node pointing relation between the sensor node in the sensor instance and the device node in the device instance, namely, carrying out association between the device instance and the sensor instance; in this way, the system modeling model 211 of the service processing system can be obtained based on the equipment class node, the equipment main node, the sensor class node and the equipment sub-node modeling, and the system modeling model is used for inquiring the equipment subordinate relation between the service equipment and the equipment sensor. That is, the system modeling model is used to record the device class nodes, the device master nodes (device nodes), the sensor class nodes, the device child nodes (sensor nodes), and the pointing relationships between the device class nodes and the device nodes, i.e., to record the device instances, the sensor instances, and the relationships between the device instances and the sensor instances.
It should be appreciated that the business scenario involved in embodiments of the present application may be an AI (Artificial Intelligence ) algorithm training scenario, such as in training a refrigeration system (refrigeration system: the core of the refrigeration system is a refrigeration unit that absorbs heat by circulating a refrigerant and then discharges the heat to achieve the cooling effect. When the service processing system comprises a plurality of service devices, the system modeling model can also record the device connection relation among the service devices, at the moment, the simulation system of the refrigerating system can be constructed based on the information recorded by the system modeling model, and then the optimal AI algorithm can be trained on the simulation system and is transferred to the refrigerating system in the physical space, so that different AI algorithms can be better compared and trained, for example, the energy consumption (PUE (Power Usage Effectiveness, power use efficiency) of the refrigerating system is selected, the energy consumption index of the data center system is evaluated, and the energy consumption ratio of all energy consumed by the data center system to the energy consumed by the IT (Internet Technology ) load is obtained. Pue=total energy consumption of the data center system/energy consumption of the IT equipment, wherein the total energy consumption of the data center system includes the energy consumption of the IT equipment and the energy consumption of the systems such as refrigeration, power distribution and the like, the value is greater than 1, and the closer to 1, the lower the energy consumption of the non-IT equipment is, the better the energy efficiency level is. ) The AI algorithm with the lowest consumption is used as the AI algorithm used by the refrigeration system to realize the intelligent refrigeration system.
For another example, the service scenario according to the embodiment of the present application may be a data query scenario, for example, when querying a relationship between a service device and a device sensor, or querying operation measurement data of the device sensor (for example, a temperature value measured by a temperature sensor in a period of operation time), a refrigeration system may be first subjected to system modeling, where the obtained system modeling model may be used to record a device instance corresponding to the service device, a sensor instance corresponding to the device sensor, and a device dependency relationship between the service device and the device sensor, and meanwhile, when the sensor metadata includes entity attribute measurement data (for example, a measurement data storage identifier, a measurement data storage location) of the device sensor, the obtained system modeling model also records a node corresponding to the measurement data storage identifier and a node corresponding to the measurement data storage location, so that when performing operation measurement data query of the related device sensor, the storage identifier node and the storage location attribute node associated with the indicated device sensor may be queried based on the system modeling model, so that the operation data of the related device sensor may be quickly queried through the storage identifier indicated by the storage identifier node and the storage location indicated by the storage identifier node, and thus the operation data may be quickly queried to implement query of the related operation data of the device at a designated time period.
Next, technical terms related to the technical field of possible application of the scheme of the embodiment of the present application are described in the following:
1. artificial intelligence:
the embodiment of the application relates to the technical field of artificial intelligence, in particular to a theory, a method, a technology and an application system which simulate, extend and expand human intelligence by using a digital computer or a machine controlled by the digital computer, sense environment, acquire knowledge and acquire an optimal result by using the knowledge. In other words, artificial intelligence is an integrated technology of computer science that attempts to understand the essence of intelligence and to produce a new intelligent machine that can react in a similar way to human intelligence. Artificial intelligence, i.e. research on design principles and implementation methods of various intelligent machines, enables the machines to have functions of sensing, reasoning and decision.
For example, machine Learning (ML) technology in artificial intelligence may be involved, where Machine Learning is a multi-domain interdisciplinary discipline involving multiple disciplines such as probability theory, statistics, approximation theory, convex analysis, algorithm complexity theory, etc. It is specially studied how a computer simulates or implements learning behavior of a human to acquire new knowledge or skills, and reorganizes existing knowledge structures to continuously improve own performance. Machine learning is the core of artificial intelligence, a fundamental approach to letting computers have intelligence, which is applied throughout various areas of artificial intelligence. Machine learning and deep learning typically include techniques such as artificial neural networks, confidence networks, reinforcement learning, transfer learning, induction learning, teaching learning, and the like.
For example, it can be understood that after the system modeling model of the service processing system is established through the technical scheme of the present application, a simulation system of the service processing system can be established based on the system modeling model, and training of an artificial intelligence algorithm (AI algorithm) is performed on the simulation system, so as to obtain the AI algorithm applicable to the service processing system.
2. Cloud technology:
cloud technology (Cloud technology) is based on the general terms of network technology, information technology, integration technology, management platform technology, application technology and the like applied by Cloud computing business models, and can form a resource pool, so that the Cloud computing business model is flexible and convenient as required. Cloud computing technology will become an important support. Background services of technical networking systems require a large amount of computing, storage resources, such as video websites, picture-like websites, and more portals. Along with the high development and application of the internet industry, each article possibly has an own identification mark in the future, the identification mark needs to be transmitted to a background system for logic processing, data with different levels can be processed separately, and various industry data needs strong system rear shield support and can be realized only through cloud computing.
For example, the method can be applied to cloud Internet of things technology. The internet of things (The Internet of Things, IOT for short) refers to collecting any object or process needing to be connected and interacted in real time through various devices and technologies such as various information sensors, radio frequency identification technologies, global positioning systems, infrared sensors, laser scanners, and the like, collecting various needed information such as sound, light, heat, electricity, mechanics, chemistry, biology, positions and the like, accessing through various possible networks, realizing ubiquitous connection of objects and people, and realizing intelligent perception, identification and management of objects and processes. The internet of things is an information carrier based on the internet, a traditional telecommunication network and the like, and enables all common physical objects which can be independently addressed to form an interconnection network.
The Cloud internet of things (Cloud IOT) aims to connect information perceived by sensors and equipment in the traditional internet of things and accepted instructions into the internet, networking is truly achieved, mass data storage and operation are achieved through a Cloud computing technology, the current running states of all 'objects' are perceived in real time due to the fact that the things are connected with each other, a large amount of data information can be generated in the process, how to collect the information, how to screen useful information in the mass information and make decision support for subsequent development, and the Cloud is a key problem affecting the development of the internet of things, and internet of things Cloud based on Cloud computing and Cloud storage technology is also a powerful support for the technology and application of the internet of things.
For example, it can be understood that a system modeling model of a service processing system in the traditional internet of things can be obtained by establishing a device instance corresponding to a service device and a sensor instance corresponding to a device sensor, and an AI algorithm is trained based on the system modeling model and applied to the service processing system, so that the service processing system is connected to the intelligent internet, and the cloud internet of things is realized.
It should be noted that, when the computer device in the embodiment of the present application obtains data such as personal data information of a user, a prompt interface or a popup window may be displayed, where the prompt interface or the popup window is used to prompt the user to collect the data such as personal data information currently, and only after obtaining that the user sends a confirmation operation to the prompt interface or the popup window, the relevant step of data obtaining is started, otherwise, the process is ended.
It will be appreciated that in particular embodiments of the present application, business data (e.g., business data tables of business processing systems, etc.) of objects such as users, businesses, institutions, systems, etc. may be involved, and when the above embodiments of the present application are applied to particular products or technologies, permissions or consents of the objects such as users, businesses, institutions, systems, etc. need to be obtained, and the collection, use and processing of relevant data need to comply with relevant laws and regulations and standards of relevant countries and regions.
Further, referring to fig. 3, fig. 3 is a system data processing method provided in an embodiment of the present application, as shown in fig. 3, the method may be performed by the above mentioned computer device, for example, any one of the service terminals or the service servers shown in fig. 3, and the method may specifically include the following steps S101 to S105, taking the computer device as an example of the service server:
s101, acquiring service metadata for system modeling from a service data table associated with a service processing system.
Wherein the service processing system comprises service equipment deployed in a physical space. The business equipment is provided with an equipment sensor. The business equipment is equipment to be subjected to system modeling, and the equipment sensor is a sensor to be subjected to system modeling. It can be appreciated that performing system modeling on the service device is a device instance for establishing the service device. The system modeling of the device sensor is to establish a sensor instance of the device sensor. In addition, there may be a plurality of service devices deployed in the service processing system, and the establishment procedure and principle of the device instance of each service device are the same, and the establishment procedure of the device instance of one service device is described here as an example. Accordingly, there may be a plurality of device sensors deployed in one service device, and the establishment procedure and principle of the sensor instance of each device sensor are the same, and the establishment procedure of the sensor instance of one device sensor is described herein as an example.
The service data table comprises N rows of table data, wherein N is a positive integer greater than 1; among the N rows of table data, the ith row of table data is used for recording the equipment data information of the business equipment, and the jth row of table data is used for recording the sensor data information of the equipment sensor (namely the collector data information of the data collector); i is not equal to j, and i and j are positive integers less than or equal to N.
Thus, the manner in which the service metadata is obtained may be: acquiring a service data table associated with a service processing system; in a service data table containing N rows of table data, when the ith row of table data in the N rows of table data is read, acquiring the equipment data information of the service equipment recorded in the ith row of table data, and taking the read equipment data information as the equipment metadata of the service equipment in a modeling mapping space corresponding to a physical space; modeling map space is different from physical space; in a business data table containing N rows of table data, when the jth row of table data in the N rows of table data is read, acquiring sensor data information of the device sensor recorded in the jth row of table data, and taking the read sensor data information as sensor metadata (namely collector metadata of a data collector) of the device sensor in a modeling mapping space; the device metadata and the sensor metadata are determined as business metadata for system modeling.
For example, the N-row table data includes table data 1 and table data 2, the table data 1 is used for recording device data information, such as the table data 1 includes data a, data B, and data C; the table data 2 is used for recording sensor data information, and the table data 2 comprises data D and data E; when the table data 1 is read, the data a, the data B and the data C read from the table data 1 are the device metadata, and when the table data 2 is read, the data D and the data E read from the table data 2 are the sensor metadata, and the data information read from the table data 1 and the table data 2 can be determined as the service metadata, namely, the device metadata (the data a, the data B and the data C) and the sensor metadata (the data D and the data E) are determined as the service metadata. The business metadata includes a plurality of metadata including device metadata of at least one business device and sensor metadata of at least one device sensor.
It will be appreciated that the relevant service personnel (modeler) may acquire a service data table provided by the service processing system, and sequentially read each row of table data from the service data table to serve as service metadata (also referred to as modeling metadata, building metadata) of the service equipment in the modeling mapping space corresponding to the physical space. That is, the modeler may be provided with a data entry template form comprising fields to be entered configured for the business device, fields to be entered configured for the device sensor, and the modeler may perform entry of form data based on the fields at the data entry template form to obtain the business data form. The field value (for example, entity name corresponding to the entity name field) recorded based on the field (for example, entity name field) required to be recorded configured for the service device is the device data information, and the field value (for example, name space corresponding to the entity name space field) recorded based on the field value (for example, entity name space field) recorded based on the field required to be recorded configured for the device sensor is the sensor data information. The data entry template form may be set by the relevant business person according to the actual modeling scenario, i.e. the information contained in the device data information may be determined according to the specific scenario, and the information contained in the sensor data information may be determined according to the specific scenario.
The modeling metadata includes device metadata of the service device in a modeling mapping space (i.e., device data information of the service device may be composed of a plurality of data for describing entity devices corresponding to the service device in the modeling mapping space), that is, metadata for performing system modeling on the service device, where the device metadata performs data representation on the service device according to a specified format (e.g., the device metadata sequentially includes entity names, entity namespaces, etc. of entity devices corresponding to the service device). It will be understood that the data obtained after the service device in the physical space is represented in a data manner may be considered as device metadata of the service device in the modeling mapping space (that is, a data set formed by a plurality of data describing entity devices corresponding to the service device in the modeling mapping space according to a specified format), and that a device instance of the service device may be established by using the device metadata. It can be understood that the digitized device mapped by the service device in the modeling mapping space may be referred to as an entity device, that is, the device instance corresponds to the entity device in the modeling mapping space, where the device node, the device class node, and the like in the device instance form the entity device, and the data space (digital space) where the entity device is located is the modeling mapping space. The node in the device instance may correspond to device information of the service device in the physical space, for example, the entity name of the entity device corresponds to the device node, the device node corresponds to the device name of the service device, and the entity name and the device name may be the same.
Accordingly, the modeling metadata includes sensor metadata of the device sensor in the modeling mapping space (i.e., sensor data information of the device sensor may be composed of a plurality of data for describing entity sensors corresponding to the device sensor in the modeling mapping space), that is, metadata for performing system modeling on the device sensor, where the sensor metadata performs data representation on the device sensor according to a specified format (e.g., the sensor metadata sequentially includes entity names, entity namespaces, etc. of entity sensors corresponding to the device sensor (i.e., actual collectors). It will be appreciated that the data obtained after the device sensor in the physical space is represented as sensor metadata for the device sensor in the modeling map space (i.e., a data set formed by a plurality of data describing the physical sensor corresponding to the device sensor in the modeling map space according to a specified format), from which sensor metadata a sensor instance for the device sensor can be created. It will be appreciated that the digitized sensors mapped in the modeling map space by the device sensors may be referred to as physical sensors, that is, the sensor instances correspond to physical sensors in the modeling map space, with the sensor nodes, sensor class nodes, etc. in the sensor instances constituting the physical sensors. The nodes in the sensor instance may correspond to sensor information of the device sensor in the physical space, for example, an entity name of the entity sensor corresponds to a sensor node, the sensor node corresponds to a sensor name of the device sensor, and the entity name and the sensor name may be the same.
It will be appreciated that the device data information of the service device and the sensor data information of the device sensor may be stored together by a service data table, where the service data table includes N rows of table data. The device data information of the service device and the sensor data information of the device sensor may be stored by a plurality of service data tables, for example, the device data information of the service device is stored by one service data table, the sensor data information of the device sensor is stored by one service data table, and the plurality of service data tables collectively comprise N rows of table data. It can be understood that when the service data table is read, when the read table data records the device data information, the data information read from the table data is the device metadata of the service device; when the service data table is read, when the read table data records sensor data information, it means that the data information read from the table data is sensor metadata of the device sensor, and all the read data information can be used as the service metadata. It will be appreciated that the service metadata includes metadata describing the entity device corresponding to the service device and in the modeling map space, and metadata describing the entity sensor corresponding to the device sensor and in the modeling map space.
S102, when the equipment type metadata of the service equipment exists in the service metadata, establishing an equipment instance of the service equipment based on the equipment type metadata.
The equipment instance is used for recording equipment class nodes and equipment nodes of the service equipment; the device node is subordinate to the device class node. The device node belongs to the device class node, and can be understood as: the device node is a child node of the device class node, or the device class node is a master node of the device node. Specifically, when the device node is subordinate to the device class node, the device node points to the device class node in the modeling map space. Further, when described later to one node (node a) subordinate to another node (node b), each means that the node a points to the node b in the modeling map space. Similarly, when it is described that one node (node a) points to another node (node b), it is indicated that the node a points to node b in the modulo mapping space, and that node a is subordinate to node b.
It can be understood that the service metadata at least includes device metadata of the service device in a modeling mapping space corresponding to the physical space. Optionally, the device metadata may include an entity name, an entity type, and an entity namespace of the entity device located in the modeling map space. It will be appreciated that the entity name is used to describe the name information of the entity device in the modeling map space, and may be the same as the name information of the business device in the physical space. The entity type is used to describe a type of an entity in the modeling map space, such as a device type or a sensor type, it is understood that when the entity type of an entity is a device type, it means that the current entity is a device entity; when the entity type of an entity is a sensor type, it means that the current entity is an entity sensor. The entity namespaces are used to describe namespaces in which device attribute types of entity devices are located. The device attribute type is used to describe a specific type of physical device, such as a refrigeration host, a cooling pump, etc. It is understood that namespaces belong to a modeling mapping space where different namespaces are used to identify and distinguish different entities and probabilities. For example, the entity device and entity sensor may be in namespaces associated with the entity in a modeler mapping space (which may be predefined by the modeler), the device attribute type of the entity device and the sensor attribute type of the entity sensor may be in namespaces associated with the attribute type in the modeler mapping space (which may be set by the modeler through the entity namespaces), and so forth. It is understood that the different namespaces constitute a modeling mapping space.
Thus, the device instance for establishing the service device based on the device class metadata may specifically be to obtain device metadata from the service metadata by traversal; if the entity type of the entity equipment is determined to be the equipment type in the equipment metadata obtained by traversing, equipment type metadata of the service equipment is determined to exist in the service metadata; and configuring equipment attribute information for the entity equipment based on the equipment type metadata, and establishing an equipment instance of the service equipment based on the configured equipment attribute information, the entity name of the entity equipment and the entity name space of the entity equipment. It will be appreciated that the device metadata of the business device may be traversed sequentially from the business metadata, and the construction of the device instance based on the device metadata when traversing to the device metadata. That is, when the entity type included in the traversed metadata is the device type, it is indicated that the metadata currently traversed is device metadata, that is, device class metadata that may indicate that service devices exist in the service metadata, it may be understood that the device metadata is device class metadata for performing system modeling, and the creation logic of the device instance is performed based on the device class metadata. That is, device attribute information may be configured for the entity device based on the device class metadata, and a device instance of the service device (i.e., a device instance representing the entity device) may be established based on the configured device attribute information, the entity name of the entity device in the device class metadata, and the entity namespace.
Among other things, it is understood that the device class metadata may include entity names, entity types, entity namespaces, and entity attribute types of entity devices to which the business devices map. It can be understood that the entity device is an entity of the service device in the modeling mapping space corresponding to the physical space. When the equipment metadata of the service equipment exists in the service metadata, the equipment instance of the service equipment is established based on the equipment metadata (namely equipment attribute information is configured for the entity equipment based on the equipment metadata, and the equipment instance of the service equipment is established based on the configured equipment attribute information, the entity name of the entity equipment and the entity name space of the entity equipment), if the entity type of the entity equipment is the equipment type, the entity name of the entity equipment in the equipment metadata is acquired, and a node configured for the entity name of the entity equipment is determined as an equipment node of the service equipment in the modeling mapping space; when the entity name space of the entity equipment belongs to a first name space, acquiring the entity attribute type of the entity equipment in the equipment type metadata, and determining a node configured for the entity attribute type of the entity equipment in the first name space as an equipment type node of the service equipment in a modeling mapping space; configuring equipment attribute information for the entity equipment based on the attribute subordinate relation between the entity name of the entity equipment and the entity attribute type of the entity equipment; and constructing a node pointing relationship between the equipment nodes and the equipment class nodes based on the configured equipment attribute information, and generating an equipment instance of the service equipment based on the node pointing relationship between the equipment nodes and the equipment class nodes. It will be appreciated that the specific entity device indicated by the entity name belongs to the device type indicated by the entity attribute type, such as entity name "temperature sensor 01" belongs to the entity attribute type "temperature sensor". Therefore, the device node corresponding to the entity name belongs to the device class node corresponding to the entity attribute type, and the device node corresponding to the entity name points to the device class node corresponding to the entity attribute type.
It may be understood that when the metadata traversed from the service metadata is device metadata, that is, when the entity type of the entity device in the traversed metadata is device type, it means that the traversed metadata is device metadata, and the entity name of the entity device is obtained from the traversed metadata (device metadata), and the node is configured for the entity name of the entity device to be used as a device node of the service device in the modeling map space. For example, a node corresponding to an entity name of an entity device may be added to a namespace associated with the entity to determine a node configured for the entity name of the entity device. For example, the configured node may be represented as: a namespace X (entity name X) indicates that a node corresponding to the entity name X, i.e., a device node, exists in the namespace X included in the modeling map space. That is, the device node is a node to which the entity name of the entity device corresponds.
It will be appreciated that the entity namespaces of the entity devices may be obtained from the traversed metadata (device metadata), and when the entity namespaces of the entity devices belong to the first namespaces, the entity attribute types of the entity devices are obtained from the traversed metadata (device metadata), and the nodes are configured for the entity attribute types of the entity devices in the first namespaces as device class nodes of the business devices in the modeling map space. For example, a node corresponding to the entity attribute type of the entity device may be added in the first namespace to determine a node configured for the entity attribute type of the entity device. For example, the configured node may be represented as: the first namespace (entity attribute type Y) indicates that there is a node corresponding to the entity attribute type Y, i.e., a device class node, in the first namespace included in the modeling map space. That is, the device class node is a node corresponding to the entity attribute type of the entity device.
Correspondingly, when the entity name space of the entity equipment belongs to the second name space, acquiring the entity attribute type of the entity equipment in the equipment type metadata, and determining the node configured for the entity attribute type of the entity equipment in the second name space as the equipment type node of the entity attribute type in the modeling mapping space. That is, the entity name space of the entity device may be obtained from the traversed metadata (device metadata), and when the entity name space of the entity device belongs to the second name space, the entity attribute type of the entity device is obtained from the traversed metadata (device metadata), and the node is configured for the entity attribute type of the entity device in the second name space to serve as the device class node of the service device in the modeling map space. For example, a node corresponding to the entity attribute type of the entity device may be added in the second namespace to determine a node configured for the entity attribute type of the entity device. For example, the configured node may be represented as: the second namespace (entity attribute type Y) indicates that there is a node corresponding to the entity attribute type Y, i.e., a device class node, in the second namespace included in the modeling map space. That is, the device class node is a node corresponding to the entity attribute type of the entity device.
The first namespace and the second namespace may refer to a space in which the entity attribute type is located, and the first namespace may be a standard namespace, for example, an existing namespace, for example, a namespace in a standard library provided by a system modeling framework (such as a brick modeling framework). The standard library contains a universal namespace provided by a brick modeling framework, and the universal namespace can define universal description terms provided for entities, such as standard attribute types of equipment, such as temperature sensors and the like. The first namespace may also be referred to as a standard namespace (brick namespace). The second namespace may be an extended namespace, such as a self-defined namespace. The self-defined namespace may have defined therein extended descriptive terms provided for entities, such as extended attribute types of devices, such as alarm sensors, etc. The second namespace may also be referred to as an extended namespace (EXT namespace).
The attribute subordinate relation between the entity name of the entity device and the entity attribute type of the entity device is used for indicating that the attribute type of the entity device corresponding to the entity name is the entity attribute type, that is, the attribute type of the device node (node a) corresponding to the entity name of the entity device is the entity attribute type corresponding to the device class node (node B) of the entity device. The attribute dependencies between the entity names and the entity attribute types may be referred to as first type attribute connections. For example, the device attribute information configured for the entity device for the entity attribute type is: a=rdf: type indicates that the attribute type of the entity device corresponding to the node a is the entity attribute type corresponding to the node B. Thus, a node-pointing relationship between a device node and a device class node may be constructed by device attribute information, that is, the node-pointing relationship is used to indicate that the device node points to the device class node, and the relationship defined by the edges between the device node and the device class node is determined based on the device attribute information. Thus, a device instance of the business device may be formed by a device node, a device class node, and a node-directed relationship between the device node and the device class node. The device instance is used for recording the node pointing relationship among the device node, the device class node and the device class node.
For example, as shown in fig. 4, fig. 4 is a schematic diagram of an establishment procedure of an apparatus example provided in an embodiment of the present application; s41, traversing and acquiring equipment metadata from service metadata; s42, determining whether the entity type of the entity equipment is the equipment type in the equipment metadata obtained through traversing; s43, if the entity type of the entity equipment is determined to be the equipment type (namely, the traversed metadata are equipment metadata), equipment type metadata of the service equipment are determined to exist in the service metadata; if it is determined that the entity type of the entity device is not the device type (i.e., the metadata traversed at this time is not the device metadata), it is determined that the device metadata of the service device does not exist in the service metadata, and step S41 is continuously executed; s44, obtaining the entity name of the entity equipment in the equipment metadata, and determining the node configured for the entity name of the entity equipment as the equipment node of the service equipment in the modeling mapping space; s45, acquiring an entity name space of entity equipment in equipment metadata; s46, when the entity name space of the entity equipment belongs to the first name space, acquiring the entity attribute type of the entity equipment in the equipment type metadata, and determining the node configured for the entity attribute type of the entity equipment in the first name space as the equipment type node of the service equipment in the modeling mapping space; s47, when the entity name space of the entity equipment belongs to a second name space, acquiring the entity attribute type of the entity equipment in the equipment type metadata, and determining the node configured for the entity attribute type of the entity equipment in the second name space as the equipment type node of the entity attribute type in the modeling mapping space; s48, configuring equipment attribute information for the entity equipment based on the attribute subordinate relation between the entity name of the entity equipment and the entity attribute type of the entity equipment; s49, constructing a node pointing relationship between the equipment node and the equipment class node based on the configured equipment attribute information; s410, generating a device instance of the service device based on the node pointing relationship between the device node and the device class node.
Optionally, a device attribute tag may also be added to the device node, so as to perform construction of a device instance based on the device node to which the attribute tag is added. The device attribute tag may be used to identify a device instance where the device node is located, for example, to distinguish device instances of different service devices, that is, to distinguish entity devices corresponding to different service devices. Such as the entity name of the entity device may be used as a device attribute tag. It will be appreciated that the device attribute tags may be defined by a modeler based on empirical values, such as entity names for entity devices or string labels generated according to certain rules, and so on. For example, when the entity type of the entity device is the device type, acquiring the entity name of the entity device in the device type metadata, and determining the node configured for the entity name as the device node of the service device in the modeling mapping space, where the entity name of the entity device is the device type, acquiring the entity name of the entity device in the device type metadata; and adding a device attribute label to the node configured for the entity name of the entity device based on the entity name of the entity device, and determining the node configured for the entity name of the entity device and added with the device attribute label as the device node of the service device in the modeling mapping space. That is, a device attribute tag corresponding to the entity name of the entity device may be added to a node configured for the entity name of the entity device. The device instance is used for recording the device node, the device class node and the node pointing relation between the device node and the device class node, which are added with the device attribute labels. Optionally, the device attribute tag may also be added to the device class node, which is not limited herein.
It will be appreciated that the process of establishing a device instance will be described herein with reference to device class metadata including, by way of example only, entity names, entity types, entity namespaces, and entity attribute types of entity devices to which the business devices are mapped. Other relevant attribute information of the entity device may also be included in the device class metadata. Such as an entity attribute model of the entity device (for describing a specific device model under the entity attribute type). Corresponding nodes may be configured for entity attribute models for use in establishing device instances. For example, a node may be configured for an entity attribute model of an entity device in a modeling mapping space to determine a device attribute node for a service device in the modeling mapping space, while a node pointing relationship between the device node and the device attribute node may be constructed based on an attribute subordinate relationship between an entity name of the entity sensor and the entity attribute model of the entity sensor, the node pointing relationship between the device node and the device attribute node is used to indicate that the device attribute node is pointed by the device node, and the relationship defined by an edge between the device node and the device attribute node indicates that the entity name of the entity device has an attribute type that is the entity attribute model of the entity device, that is, the device node (node C) corresponding to the entity name of the entity device has an attribute type that is the entity attribute model corresponding to the device attribute node (node D) of the entity device. That is, the attribute type of the entity device corresponding to the node C is the entity attribute model corresponding to the node D. At this time, the device instance of the service device may be formed by a device node, a device class node, a device attribute node, a node pointing relationship between the device node and the device attribute node, and a node pointing relationship between the device node and the device class node. The device instance is used for recording the device node, the device class node, the device attribute node, the node pointing relationship between the device node and the device attribute node and the node pointing relationship between the device node and the device class node.
It will be understood that, equivalently, after the device instance for recording the device node, the device class node, and the node pointing relationship between the device node and the device class node is established, the device instance is updated by the device attribute node and the node pointing relationship between the device node and the device attribute node, and the updated device instance is used for recording the device node, the device class node, the device attribute node, the node pointing relationship between the device node and the device attribute node, and the node pointing relationship between the device node and the device class node. That is, the principle of configuring nodes by data information included in the device class metadata to construct device instances is the same, that is, after the device instances for recording the device nodes, the device class nodes, and node pointing relationships between the device nodes and the device class nodes are established, if the device class metadata further includes other data information besides entity names, entity types, entity namespaces, and entity attribute types, the nodes and the node pointing relationships between the device nodes may be configured for other data information to update the aforementioned device instances. The data information included in the device class metadata is not limited herein, and may be expanded as the service progresses.
For example, as shown in fig. 5 to fig. 6, fig. 5 to fig. 6 are schematic diagrams of an establishment scenario of an apparatus example provided by an embodiment of the present application; the device class metadata in fig. 5 includes entity names, entity types, entity namespaces and entity attribute types of entity devices mapped by the service devices; determining a node configured for the entity name of the entity device as a device node 52 of the service device in the modeling mapping space 51; when the entity namespace of the entity device belongs to a first namespace (or a second namespace), acquiring the entity attribute type of the entity device in the device class metadata, and determining a node configured for the entity attribute type of the entity device in the first namespace (or the second namespace) (collectively called a namespace 53) as a device class node 54 of the service device in a modeling mapping space; configuring device attribute information 55 for the entity device based on an attribute membership between an entity name of the entity device and an entity attribute type of the entity device; node orientation relation 56 between the device node and the device class node is constructed based on the device attribute information (the node orientation relation indicates that the device node points to the device class node, and the relation of edges between the device node and the device class node is a, a=rdf:type, i.e. a first type attribute connection relation), so as to build and obtain a device instance in the modeling mapping space 51, where the device instance built and obtained includes: device node 52, device class node 54 in namespace 53, and node-directed relationship 56 between device node 52 and device class node 54.
Further, as shown in fig. 6, the above-mentioned device class metadata shown in fig. 5 further includes an entity attribute model of the entity device, a node configured for the entity attribute model of the entity device may be determined as a device attribute node 57 of the service device in the modeling mapping space, a node pointing relationship 58 between the device node and the device attribute node is constructed (the node pointing relationship indicates that the device node points to the device attribute node, and a relationship of an edge between the device node and the device attribute node is B, "B" is used to indicate that the device model of the entity device corresponding to the device node is the entity attribute model indicated by the device attribute node, and b=rdf: types) to update the device instance in fig. 5, so as to obtain an updated device instance, where the updated device instance includes: device node 52, device class node 54 in namespace 53, node-directed relationship 56 between device node 52 and device class node 54, and node-directed relationship 58 between device node 52 and device attribute node 57 are newly added to device attribute node 57.
Optionally, the device metadata may include an entity name, an entity type of the entity device located in the modeling map space. Thus, when the entity type of the entity device is the device type, the device instance of the service device may be that, when the entity type of the entity device is the device type, the entity name of the entity device in the device metadata is obtained, and the node configured for the entity name of the entity device is determined to be the device node of the service device in the modeling mapping space, the entity type of the entity device in the device metadata is obtained, and the node configured for the entity type of the entity device is determined to be the device class node of the service device in the modeling mapping space, and based on the attribute subordinate relationship between the entity name of the entity device and the entity attribute type of the entity device, the device attribute information is configured for the entity device, and based on the configured device attribute information, the node pointing relationship between the device node and the device class node is constructed, and the device instance of the service device is generated based on the node pointing relationship between the device node and the device class node. It can be understood that the namespace in which the device node is located and the namespace in which the device class node is located may be the same space or different spaces, and may be defined by a modeler.
S103, when the sensor class metadata of the device sensors deployed on the service device exist in the service metadata, the sensor instance of the device sensors is built based on the sensor class metadata.
Wherein the sensor instance is used for recording sensor class nodes and sensor nodes of the device sensor; the sensor nodes are subordinate to the sensor class nodes. The sensor node is subordinate to the sensor class node, and the sensor node is understood to be a child node of the sensor class node or a main node of the sensor class node. In other words, when a sensor node is subordinate to a sensor class node, the sensor node points to the sensor class node in the modeling map space.
It can be understood that the service metadata at least includes sensor metadata of the device sensor in a modeling mapping space corresponding to the physical space. Alternatively, the sensor metadata may include entity names, entity types, and entity namespaces of entity sensors located in the modeling map space. It will be appreciated that the entity name is used to describe the name information of the entity sensor in the modeling map space, which may be the same as the name information of the device sensor in the physical space. The entity type is used to describe a type of an entity in the modeling map space, such as a device type or a sensor type, it is understood that when the entity type of an entity is a device type, it means that the current entity is a device entity; when the entity type of an entity is a sensor type, it means that the current entity is an entity sensor. The entity namespaces are used to describe namespaces in which the sensor attribute types of the entity sensors are located. The sensor attribute type is used to describe a specific type of physical sensor, such as a temperature sensor, a pressure sensor, etc. For a specific description of namespaces, reference may be made to the step-related description above.
Thus, the process and principle of creating a sensor instance of a device sensor based on the sensor class metadata is the same as the process and principle of creating a device instance of a business device based on the device class metadata. The method specifically comprises the steps of traversing and acquiring sensor metadata from service metadata; if the entity type of the entity sensor is determined to be the sensor type in the sensor metadata obtained by traversing, determining that the sensor type metadata of the equipment sensor exists in the service metadata; configuring sensor attribute information for the entity sensor based on the sensor class metadata, and establishing a sensor instance of the device sensor based on the configured sensor attribute information, the entity name of the entity sensor and the entity namespace of the entity sensor.
It will be appreciated that the sensor metadata of the device sensor may be traversed sequentially from the business metadata and the construction of the sensor instance based on the sensor metadata as it is traversed to the sensor metadata. That is, when the entity type included in the traversed metadata is a sensor type, it is indicated that the currently traversed metadata is sensor metadata, that is, sensor class metadata, which may indicate that there is a device sensor in the service metadata, it is understood that the sensor metadata is sensor class metadata for performing system modeling, and the creation logic of a sensor instance is performed based on the sensor class metadata. That is, sensor attribute information may be configured for the entity sensor based on the sensor class metadata, and a sensor instance of the device sensor (i.e., a sensor instance representing the entity sensor) may be established based on the configured sensor attribute information, the entity name of the entity sensor in the sensor class metadata, and the entity namespace.
Among other things, it is understood that the sensor class metadata may include entity names, entity types, entity namespaces, and entity attribute types of entity sensors to which the device sensors are mapped. It is understood that the entity sensor is an entity of the device sensor in a modeling map space corresponding to the physical space. When the sensor class metadata of the device sensor exists in the service metadata, the sensor instance of the device sensor is established based on the sensor class metadata (namely, the sensor attribute information is configured for the entity sensor based on the sensor class metadata, the sensor instance of the device sensor is established based on the configured sensor attribute information, the entity name of the entity sensor and the entity naming space of the entity sensor), and when the entity type of the entity sensor is the sensor type, the entity name of the entity sensor in the sensor class metadata is acquired, and the node configured for the entity name of the entity sensor is determined as the sensor node of the device sensor in the modeling mapping space; when the entity name space of the entity sensor belongs to a first name space, acquiring the entity attribute type of the entity sensor in the sensor class metadata, and determining a node configured for the entity attribute type of the entity sensor in the first name space as a sensor class node of the equipment sensor in a modeling mapping space; configuring sensor attribute information for the entity sensor based on an attribute subordinate relation between the entity name of the entity sensor and the entity attribute type of the entity sensor; and constructing a node pointing relationship between the sensor nodes and the sensor class nodes based on the configured sensor attribute information, and generating a sensor instance of the device sensor based on the node pointing relationship between the sensor nodes and the sensor class nodes.
It will be appreciated that when the metadata traversed from the service metadata is sensor metadata, that is, when the entity type of the entity sensor in the traversed metadata is sensor type, it means that the traversed metadata is sensor metadata, and the entity name of the entity sensor is obtained from the traversed metadata (sensor metadata), and the node is configured for the entity name of the entity sensor to be a sensor node in the modeling map space of the device sensor. For example, a node corresponding to an entity name of an entity sensor may be added to a namespace associated with the entity to determine a node configured for the entity name of the entity sensor. For example, the configured node may be represented as: a namespace X (entity name X) indicates that a node corresponding to the entity name X, i.e., a sensor node, exists in the namespace X included in the modeling map space. That is, the sensor node is a node to which the entity name of the entity sensor corresponds.
It will be appreciated that the entity namespaces of the entity sensors may be obtained from the traversed metadata (sensor metadata), that when the entity namespaces of the entity sensors belong to the first namespaces, the entity attribute types of the entity sensors are obtained from the traversed metadata (sensor metadata), and that nodes are configured in the first namespaces for the entity attribute types of the entity sensors as sensor class nodes in the device sensors modeling map space. For example, a node corresponding to the entity attribute type of the entity sensor may be added in the first namespace to determine a node configured for the entity attribute type of the entity sensor. For example, the configured node may be represented as: the first namespace (entity attribute type Y) indicates that there is a node corresponding to the entity attribute type Y, i.e., a sensor class node, in the first namespace included in the modeling map space. That is, the sensor class node is a node corresponding to the entity attribute type of the entity sensor.
Correspondingly, when the entity namespaces of the entity sensors belong to the second namespaces, the entity attribute types of the entity sensors in the sensor class metadata are acquired, and the nodes configured for the entity attribute types of the entity sensors in the second namespaces are determined as sensor class nodes of the entity attribute types in the modeling mapping space. That is, the entity namespace of the entity sensor may be obtained from the traversed metadata (sensor metadata), and when the entity namespace of the entity sensor belongs to the second namespace, the entity attribute type of the entity sensor is obtained from the traversed metadata (sensor metadata), and the node is configured in the second namespace for the entity attribute type of the entity sensor as a sensor class node of the device sensor in the modeling map space. For example, a node corresponding to the entity attribute type of the entity sensor may be added in the second namespace to determine a node configured for the entity attribute type of the entity sensor. For example, the configured node may be represented as: the second namespace (entity attribute type Y) indicates that there is a node corresponding to the entity attribute type Y, i.e., a sensor class node, in the second namespace included in the modeling map space. That is, the sensor class node is a node corresponding to the entity attribute type of the entity sensor. Wherein, the specific description of the first naming space and the second naming space can be referred to the related description of the steps.
The attribute subordinate relation between the entity name of the entity sensor and the entity attribute type of the entity sensor is used for indicating that the entity name of the entity sensor has an attribute type that is the entity attribute type of the entity sensor, that is, the attribute type of the sensor node (node a) corresponding to the entity name of the entity sensor is the entity attribute type corresponding to the sensor class node (node B) of the entity sensor. The sensor attribute information configured for the physical sensor is, for example: a=rdf: type indicates that the attribute type of the entity sensor corresponding to the node a is the entity attribute type corresponding to the node B. Thus, a node pointing relationship between a sensor node and a sensor class node may be constructed by the sensor attribute information, that is, the node pointing relationship is used to indicate that the sensor node points to the sensor class node, and the relationship defined by the edges between the sensor node and the sensor class node is the sensor attribute information. Thus, a sensor instance of a device sensor may be composed by a sensor node, a sensor class node, and a node pointing relationship between the sensor node and the sensor class node. The sensor instance is used to record the sensor nodes, the sensor class nodes, and the node pointing relationships between the sensor nodes and the sensor class nodes.
Optionally, a sensor attribute tag may also be added to the sensor node to construct a sensor instance based on the sensor node to which the attribute tag is added. The sensor attribute tag may be used to identify a sensor instance where a sensor node is located, e.g. to distinguish between sensor instances of different device sensors, i.e. to distinguish between corresponding physical sensors of different device sensors. For example, the entity name of the entity sensor can be used as a sensor attribute label. It will be appreciated that the sensor attribute tags may be defined by a modeler based on empirical values, such as entity names for entity sensors or string labels generated according to certain rules, and so forth. For example, when the entity type of the entity sensor is the sensor type, acquiring the entity name of the entity sensor in the sensor type metadata, determining the node configured for the entity name as the sensor node of the device sensor in the modeling mapping space, and when the entity type of the entity sensor is the sensor type, acquiring the entity name of the entity sensor in the sensor type metadata; and adding a sensor attribute label to the nodes configured for the entity names of the entity sensors based on the entity names of the entity sensors, and determining the nodes configured for the entity names of the entity sensors and added with the sensor attribute label as sensor nodes of the device sensors in the modeling mapping space. That is, a sensor attribute tag corresponding to the entity name of the entity sensor may be added to a node configured for the entity name of the entity sensor. The sensor instance is used for recording the sensor nodes added with the sensor attribute labels, the sensor class nodes and the node pointing relation between the sensor nodes and the sensor class nodes. Alternatively, the sensor attribute tag may be further added to the sensor class node, which is not limited herein.
It will be appreciated that the process of creating a sensor instance will be described herein with respect to sensor class metadata including entity names, entity types, entity namespaces, and entity attribute types of entity sensors mapped by a device sensor. Other relevant attribute information of the entity sensor may also be included in the sensor class metadata. Such as the physical attribute model of the physical sensor (for describing the specific sensor model under the physical attribute type), etc., and the sensor class metadata may specifically include data that may be referred to in the following description of the embodiments, and is described herein by way of example only in terms of the physical attribute model. Corresponding nodes may be configured for entity attribute models for use in establishing sensor instances. For example, nodes may be configured for entity attribute models of entity sensors in a modeling mapping space to determine the entity attribute nodes of the entity sensors in the modeling mapping space as device sensors, while node pointing relationships between the sensor nodes and the entity attribute nodes may be constructed based on attribute affiliations between entity names of the entity sensors and entity attribute models of the entity sensors, the node pointing relationships between the sensor nodes and the sensor attribute nodes are used for indicating that the sensor attribute nodes are pointed by the sensor nodes, and the relationships defined by edges between the sensor nodes and the sensor attribute nodes indicate that the entity names of the entity sensors have attribute types that are entity attribute models of the entity sensors, that is, the attribute types of the sensor nodes (node C) corresponding to the entity names of the entity sensors are entity attribute models corresponding to the sensor attribute nodes (node D) of the entity sensors. That is, the attribute type of the entity sensor corresponding to the node C is the entity attribute model corresponding to the node D. At this time, a sensor instance of the device sensor may be constituted by a sensor node, a sensor class node, a sensor attribute node, a node pointing relationship between the sensor node and the sensor attribute node, and a node pointing relationship between the sensor node and the sensor class node. The sensor instance is used for recording the sensor node, the sensor class node, the sensor attribute node, the node pointing relationship between the sensor node and the sensor attribute node and the node pointing relationship between the sensor node and the sensor class node.
It is understood that it is equivalent to updating the sensor instance by the sensor attribute node and the node pointing relationship between the sensor node and the sensor attribute node after the sensor instance for recording the node pointing relationship between the sensor node, the sensor class node, and the sensor node and the sensor class node is established, and the updated sensor instance is used for recording the node pointing relationship between the sensor node, the sensor class node, the sensor attribute node, the sensor node and the sensor attribute node, and the node pointing relationship between the sensor node and the sensor class node. That is, the principle of configuring nodes by data information included in the sensor class metadata to construct a sensor instance is the same, that is, after the sensor instance for recording the sensor node, the sensor class node, and the node pointing relationship between the sensor node and the sensor class node is constructed, if the sensor class metadata further includes other data information except for entity name, entity type, entity namespace, and entity attribute type, the nodes and the node pointing relationship between the sensor node and the other data information may be configured to update the aforementioned sensor instance. The data information included in the sensor class metadata is not limited herein, and may be expanded as the service progresses. The specific establishment procedure of the sensor instance of the entity sensor can be seen from the related description of the following embodiments.
Alternatively, the sensor metadata may include entity names, entity types, of entity sensors located in the modeling map space. Thus, the sensor instance of the device sensor may be that, when the entity type of the entity sensor is a sensor type, the entity name of the entity sensor in the sensor metadata is acquired, and the node configured for the entity name of the entity sensor is determined as a sensor node of the device sensor in the modeling mapping space, the entity type of the entity sensor in the sensor metadata is acquired, and the node configured for the entity type of the entity sensor is determined as a sensor class node of the device sensor in the modeling mapping space, the sensor attribute information is configured for the entity sensor based on the attribute subordinate relation between the entity name of the entity sensor and the entity attribute type of the entity sensor, and the node pointing relation between the sensor node and the sensor class node is constructed based on the configured sensor attribute information, and the sensor instance of the device sensor is generated based on the node pointing relation between the sensor node and the sensor class node. It can be understood that the namespace where the sensor nodes are located and the namespace where the sensor class nodes are located may be the same space or different spaces, and may be defined by a modeler.
S104, based on the device subordination relation between the service device and the device sensor, configuring the device node in the device instance as a device master node, and configuring the sensor node in the sensor instance as a device child node subordinate to the device master node.
Wherein the device dependency relationship is used to indicate that the device sensor deployed in the service device belongs to the service device, i.e. the first type of device connection relationship. The device affiliation may be obtained from sensor metadata, for example, the sensor metadata may further include device information (which may represent the device affiliation) of the entity sensor, where the device information is used to indicate an entity name of the entity device in the modeling mapping space for the business device deploying the device sensor corresponding to the entity sensor. Thus, the device instance and the sensor instance may be automatically associated by the belonging device information provided in the sensor metadata, i.e. the device node in the device instance and the sensor node in the sensor entity. The sensor node is subordinate to the device node, i.e. the sensor node is used for pointing to the device node. That is, the sensor node acts as a device sub-node, the device node acts as a device master node, and the device sub-node points to the device master node. At the same time, a node-directed relationship between the sensor node and the device node may be defined, which may be used to point to device dependencies. For example, the node pointing relationship is used to indicate that the sensor node points to the device node, and the relationship of the edges between the sensor node and the device node is that the device to which the device sensor corresponding to the sensor node belongs is the service device corresponding to the device node, for example, the relationship of the edges between the sensor node and the device node is defined as: brick, isPointOf.
S105, based on the equipment class node, the equipment main node, the sensor class node and the equipment sub-node, a system modeling model of the service processing system is obtained through modeling.
The system modeling model is used for inquiring the device subordinate relation between the service device and the device sensor. That is, the modeled system modeling model is used to record device class nodes, device master nodes, sensor class nodes, device child nodes, and device dependencies between device master nodes and device child nodes. Therefore, the device dependency relationship between the service device corresponding to the device master node and the device sensor corresponding to the device child node can be obtained through the device dependency relationship inquiry between the device master node and the device child node recorded by the system modeling model.
For example, as shown in fig. 7, fig. 7 is a schematic view of a scenario for establishing a system modeling model according to an embodiment of the present application; when traversing from the service metadata to the device class metadata 71 of the service device, establishing a device instance 72 of the service device based on the device class metadata, wherein the device instance comprises a device node 73 corresponding to an entity name of an entity device corresponding to the service device and a device class node 74 corresponding to an entity attribute type of the entity device, the device node points to the device class node, and the relationship between the device node and the device class node is a (a=rdf: type, the display information of the edge is not limited and can be configured by a modeler, such as a first type attribute connection relationship); when traversing from the service metadata to the sensor class metadata 75 of the device sensor, establishing a sensor instance 76 of the device sensor based on the sensor class metadata, wherein the sensor instance comprises a sensor node 77 corresponding to the entity name of the entity sensor corresponding to the device sensor and a sensor class node 78 corresponding to the entity attribute type of the entity sensor, the sensor node points to the sensor class node, and the relation between the sensor node and the sensor class node is A; the node pointing relationship 710 between the device node and the sensor node may be established based on the device subordinate relationship 79 between the service device and the device sensor, where the node pointing relationship is used to indicate that the device node is pointed by the sensor node, and the relationship between the sensor node and the device node is brick, that is, ispintof (the display information of the edge is not limited and may be configured by a modeler, such as a first type device connection relationship), so as to obtain a system modeling model of the service processing system. It is understood that the sensor node points to the device node may be understood that the device sensor corresponding to the sensor node belongs to the service device corresponding to the device node.
It can be appreciated that a plurality of service devices can be included in the service processing system, each service device can obtain a corresponding device instance, and a device sensor deployed in each service device can obtain a corresponding sensor instance. That is, the system modeling model obtained by modeling at this time includes device instances corresponding to the respective service devices, and sensor instances corresponding to the device sensors in the respective service devices. It will be appreciated that for a service device in a service processing system, there is a connection relationship between the service device and the service device, e.g. the service device a includes the service device B, and then there is a device connection relationship between the service device a and the service device B in physical space. For example, the service device a is an upstream device of the service device B, and then the service device a and the service device B have a device connection relationship in a physical space. The device instance of the service device a and the device instance of the service device B can thus be associated by means of a device connection relationship between the service device a and the service device B, that is to say the device node in the device instance of the service device a and the device node in the device instance of the service device B.
The service processing system includes two service devices, for example, the service devices include a first service device and a second service device, and when the service processing system includes more service devices, the process of associating the service devices is the same. Therefore, based on the device connection relation between the first service device and the second service device in the physical space, the device node pointing relation between the device node in the device instance of the first service device and the device node in the device instance of the second service device can be constructed; updating a system modeling model of the service processing system based on the equipment node pointing relation to obtain an updated system modeling model; the updated system modeling model is used for inquiring the device connection relation between the first service device and the second service device. Optionally, when the device connection relationship between the first service device and the second service device is a device containing relationship (third type device connection relationship), and the first service device contains the second service device, the device node pointing relationship may be used to indicate that a device node in a device instance corresponding to the second service device (where the device node in the device instance corresponding to the second service device may be regarded as a device child node) points to a device node in a device instance corresponding to the first service device (where the device node in the device instance corresponding to the first service device may be regarded as a device master node), and the relationship of edges between the nodes is used to indicate that the second service device belongs to the first service device (such as a bridge: belongto, third type device connection relationship). Alternatively, when the device connection relationship between the first service device and the second service device is a device upstream-downstream relationship (a second type device connection relationship), and the first service device is an upstream device and the second service device is a downstream device, the device node pointing relationship may be used to indicate that the device node in the device instance corresponding to the first service device (where the device node in the device instance corresponding to the first service device may be regarded as a device child node) points to the device node in the device instance corresponding to the second service device (where the device node in the device instance corresponding to the second service device may be regarded as a device master node), and the edge relationship between the nodes is used to indicate that the first service device is an upstream device (such as a bridge. It will be appreciated that the node pointing relationships between device nodes may be different for different device connection relationships, which may be set by modelers based on empirical values, which are merely examples and not limiting.
It may be appreciated that, when the system modeling device includes a device instance of the first service device and a device instance of the second service device, a device node pointing relationship between a device node in the device instance of the first service device and a device node in the device instance of the second service device may be updated in the established system modeling device. The service processing model obtained in this way can query and analyze not only the relationship between the service equipment and the equipment sensor, but also the relationship between the service equipment and the service equipment.
Alternatively, the device connection relationship between the business device and the business device may be provided in the device metadata (i.e., automatic modeling is implemented), or may be additionally written by the modeler (i.e., manual modeling). For example, the device metadata may include downstream device information (the downstream device information may represent a device connection relationship) of the entity device, where the downstream device information is used to indicate an entity name of a downstream entity device of the entity device corresponding to the service device in the modeling mapping space (that is, a device name of a downstream service device of the service device in the physical space), and through the downstream device information, a device node corresponding to the entity device may be pointed to a device node corresponding to the downstream entity device. For another example, the device metadata may include information of a device to which the entity device corresponds (the information of the device may represent a device connection relationship), where the information of the device is used to indicate an entity name of the entity device to which the entity device corresponds in the modeling mapping space (that is, a device name of the service device to which the service device belongs in the physical space), and through the information of the device to which the entity device corresponds may be caused to point to a device node corresponding to the entity device to which the entity device corresponds.
For example, as shown in fig. 8, fig. 8 is a schematic view of a scenario for creating a system modeling model according to an embodiment of the present application; the service processing system comprises a first service device A1, a second service device A2 and a third service device A3, wherein the first service device belongs to the second service device, and the third service device is downstream equipment of the second service device; the first service equipment is provided with a first equipment sensor B1, the second service equipment is provided with a second equipment sensor B2, and the third service equipment is provided with a third equipment sensor B3; the device instance 81 of the first service device A1 (including the first device node 82, the first device class node 83, and the node pointing relationship between the first device node and the first device class node, and the edge relationship between the nodes is a, a=rdf: type, the first type attribute connection relationship (LK 1)), the device instance 84 of the second service device A2 (including the second device node 85, the second device class node 86, and the node pointing relationship between the second device node and the second device class node, and the edge relationship between the nodes is a), the device instance 87 of the third service device A3 (including the third device node 88, the third device class node 89, and the node pointing relationship between the third device node and the third device class node, and the edge relationship between the nodes is a), the sensor instance 810 of the first device sensor B1 (including the first sensor node 811, the first sensor class node 812, and the edge relationship between the first sensor node and the first sensor class node 814, and the edge relationship between the second sensor node and the third sensor node 816, and the edge relationship between the sensor node and the third sensor node 813 is the third device node, and the third sensor node point relationship between the third sensor node 816 and the third sensor node point relationship between the third device class node 813 and the third device class node point between the third device node and the third device class node point; configuring the first device node as a first device master node based on a device slave between the first service device and the first device sensor, configuring the first sensor node as a first device child node for pointing to the first device master node; configuring the second device node as a second device master node based on a device slave between the second service device and the second device sensor, configuring the second sensor node as a second device child node for pointing to the second device master node; configuring a third device node as a third device master node based on a device slave between the third service device and the third device sensor, and configuring the third sensor node as a third device child node for pointing to the third device master node; in this way, the first device instance and the first sensor instance may be associated (an edge relationship between the first device main node and the first device sub-node is brick: isPointOf, a first type device connection relationship (LK 2)), the second device instance and the second sensor instance may be associated (an edge relationship between the second device main node and the second device sub-node is brick: isPointOf), the third device instance and the third sensor instance may be associated (an edge relationship between the third device main node and the third device sub-node is brick: isPointOf), and a system modeling model of the service processing system may be further established by the first device class node, the first device main node, the first sensor class node, the first device sub-node, the second device class node, the second device main node, the second sensor class node, the second device sub-node, the third device class node, the third device main node, the third sensor class node and the third device sub-node; further, a device node pointing relationship (i.e., a third type device connection relationship (LK 3) between the first device node and the second device node may be determined according to a device connection relationship between the first service device and the second service device in the physical space, the first device node 82 may be indicated to point to the second device node 85, and a side relationship between the nodes may be a bridge: belongto), and a device node pointing relationship (i.e., a second type device connection relationship (LK 4)) between the second device node and the third device node may be determined according to a device connection relationship between the second service device and the third service device, the second device node 85 may be indicated to point to the third device node 88, and a side relationship between the nodes may be a bridge. The updated system modeling model is used for recording the association relation between the business devices and the device sensors.
Optionally, after the final system modeling model is obtained, the nodes in the final system modeling model may be merged, for example, the same nodes in the final system modeling model are merged, for example, the entity attribute type of the entity sensor corresponding to the first device sensor in the first service device is the same as the entity attribute type of the entity sensor corresponding to the second device sensor in the second service device, so that the node 1 corresponding to the entity attribute type of the entity sensor corresponding to the first device sensor is the same as the node 2 corresponding to the entity attribute type of the entity sensor corresponding to the second device sensor in the second service device in the system modeling model, and therefore, the node 1 and the node 2 may be merged to reduce the memory size of the system modeling model.
In the embodiment of the application, the service metadata for carrying out system modeling can be acquired from the service data table associated with the service processing system, and when the equipment type metadata of the service equipment exists in the service metadata, the equipment instance of the service equipment is established based on the equipment type metadata, and the equipment instance is used for recording the equipment type nodes of the service equipment in the service processing system and the equipment nodes for pointing to the equipment type nodes; the device instance can be automatically constructed based on the device metadata, so that the service device is mapped from a physical space to a modeling mapping space, namely, the service device which is actually present is subjected to data structuring, so that the datamation entity device corresponding to the service device is obtained, and the data space (digital space) where the entity device is located is the modeling mapping space; similarly, when the sensor class metadata of the device sensors deployed on the service equipment exist in the service metadata, a sensor instance of the device sensors is established based on the sensor class metadata, wherein the sensor instance is used for recording sensor class nodes of the device sensors in the service equipment and the sensor nodes pointing to the sensor class nodes; in this way, the automatic construction of the sensor instance can be performed based on the sensor metadata so as to map the equipment sensor from the physical space to the modeling mapping space, namely, the data structure of the equipment sensor which exists truly is realized so as to obtain the entity sensor which corresponds to the equipment sensor and has the data; in addition, the device node in the device instance can be configured as a device master node based on the device subordinate relation (such as recorded in a service data table) between the service device and the device sensor, and the sensor node in the sensor instance is configured as a device child node for pointing to the device master node, so that the association between the entity device and the entity sensor is automatically performed in the modeling mapping space, and the service device, the device sensor and the device subordinate relation between the service device and the device sensor in the service processing system can be digitally represented based on the system modeling model obtained by modeling the device class node, the device master node, the sensor class node and the device child node; it can be understood that a modeler can realize system modeling of the service processing system only by providing the service data table without performing a great deal of complicated operations, so that the system modeling process of the service processing system can be optimized, the complexity and difficulty of the whole system modeling process are reduced, and the system modeling efficiency and modeling convenience for the service processing system are further improved.
Further, referring to fig. 9, fig. 9 is a system data processing method provided in an embodiment of the present application, as shown in fig. 9, the method may be performed by the above mentioned computer device, for example, any one of the service terminals or the service servers shown in fig. 9, and the method may specifically include the following steps S201 to S206, taking the computer device as an example of the service server:
s201, acquiring service metadata for system modeling from a service data table associated with a service processing system.
S202, when the equipment type metadata of the service equipment exists in the service metadata, establishing an equipment instance of the service equipment based on the equipment type metadata. The specific implementation of steps S201 to S202 may be referred to the related description of the above embodiments, which is not repeated herein.
S203, when the sensor class metadata of the device sensors deployed on the service devices exist in the service metadata, establishing sensor instances of the device sensors based on the sensor class metadata.
Wherein the sensor instance is used for recording sensor class nodes and sensor nodes of the device sensor. The sensor nodes are subordinate to the sensor class nodes.
The sensor class metadata may include, among other things, entity names, entity types, entity namespaces, and entity attribute types of entity sensors to which the device sensors map. The entity type may be used to indicate that metadata traversed from the business metadata is sensor class metadata or device class metadata. When traversing to the sensor class data, a sensor instance of the device sensor may be established by an entity name, an entity namespace, and an entity attribute type in the sensor class metadata. Reference is made to the description of the above embodiments for a specific implementation of the set-up sensor example. The sensor instance established at this time comprises a sensor node corresponding to the entity name, a sensor class node corresponding to the entity attribute type in the entity name space, and a node pointing relation between the sensor node and the sensor class node.
Optionally, the sensor metadata may further include an entity property measurement unit of the entity sensor, which entity property measurement unit may be used to indicate a unit of operational measurement data of the entity sensor. For example, the entity sensor is an entity of the temperature sensor in the modeling map space, and the unit of measurement may be degrees celsius. For example, the entity sensor is an entity of the switch sensor in the modeling mapping space, and the measurement unit is a unit-free unit. Therefore, the node configured for the entity attribute measurement unit of the entity sensor can be determined as the first sensor attribute node of the device sensor in the modeling mapping space; constructing a node pointing relationship between a sensor node and a first sensor attribute node based on an attribute subordinate relationship between an entity name of an entity sensor and an entity attribute measurement unit of the entity sensor; the sensor instance of the device sensor is updated based on the node pointing relationship between the sensor node and the first sensor attribute node. For example, a node corresponding to an entity property measurement unit of an entity sensor may be added to a namespace associated with the measurement unit to determine a node configured for the entity property measurement unit of the entity sensor. For example, the configured node may be represented as: a namespace Z (entity attribute measurement unit Z) indicates that a node corresponding to the entity attribute measurement unit Z, i.e., a first sensor attribute node, exists in the namespace Z included in the modeling map space. That is, the first sensor attribute node is a node corresponding to an entity attribute measurement unit of the entity device.
The attribute subordinate relation between the entity name of the entity sensor and the entity attribute measurement unit of the entity sensor is used to indicate that the measurement unit of the entity sensor corresponding to the entity name is the entity attribute measurement unit, that is, the measurement unit of the sensor node (node a) corresponding to the entity name of the entity sensor is the entity attribute measurement unit corresponding to the first sensor attribute node (node C) of the entity sensor. For example, sensor attribute information (sensor attribute information a) configured for an entity sensor for a measurement unit is used to indicate the relationship of edges between the node a and the node C as: the brick is hasUnit, which indicates that the entity sensor corresponding to the node A has a measurement unit of entity attribute corresponding to the node C. Thus, a node pointing relationship between the sensor node and the first sensor attribute node may be constructed by the sensor attribute information a, that is, the node pointing relationship is used to indicate that the first sensor attribute node is pointed to by the sensor node, and the relationship defined by the edge between the sensor node and the first sensor attribute node is determined based on the sensor attribute information a. Thus, the sensor instance of the traffic sensor may be updated by the first sensor attribute node, the node pointing relationship between the sensor node and the first sensor attribute node. The sensor instance is also configured to record the first sensor attribute node, the node pointing relationship between the sensor node and the first sensor attribute node.
Accordingly, the sensor metadata may also include entity attribute measurement data of the entity sensor, which may be used to indicate stored information of operational measurement data of the entity sensor, such as the entity attribute measurement data may include a measurement data storage identity and a measurement data storage location. The measurement data storage location may be used to indicate a storage location (e.g., a database or data file) for operational measurement data of the physical sensor, and the measurement data storage identifier may be used to indicate a storage identifier in the storage location for operational measurement data of the physical sensor (e.g., the operational measurement data of the temperature sensor is temperature, and the storage identifier may be temperature data a). Therefore, the node configured for the physical attribute measurement data of the physical sensor can be determined as a second sensor attribute node of the device sensor in the modeling mapping space; constructing a node pointing relationship between a sensor node and a second sensor attribute node based on the attribute subordinate relationship between the entity name of the entity sensor and the entity attribute measurement data of the entity sensor; the sensor instance of the device sensor is updated based on the node pointing relationship between the sensor node and the second sensor attribute node.
The node configured for the entity attribute measurement data of the entity sensor can be a node configured for the measurement data storage identification of the entity sensor, and is determined to be a storage identification attribute node of the equipment sensor in a modeling mapping space; determining a node configured for a measured data storage location of the entity sensor as a storage location attribute node of the device sensor in a modeling mapping space; a target storage attribute node associated with the storage identification attribute node and the storage location attribute node is generated, and a node configured for entity attribute measurement data of the entity sensor is determined based on the target storage attribute node. That is, the target storage attribute node is determined to be the node configured for the physical attribute measurement data of the physical sensor. Wherein the target storage attribute node is subordinate to the storage identification attribute node and subordinate to the storage location attribute node. That is, the target storage attribute node points to the storage identification attribute node and to the storage location attribute node in the modeling map space.
For example, it may be to add a node corresponding to the measurement data store identification of the entity sensor in the namespace associated with the measurement data to determine a node configured for the measurement data store identification of the entity sensor. For example, the configured node may be represented as: a namespace W (measurement data storage identifier W) indicates that a node corresponding to the measurement data storage identifier W, that is, a storage identifier attribute node, exists in the namespace W included in the modeling map space. That is, the storage identification attribute node is a node to which the measurement data storage identification of the entity device corresponds. Likewise, a node corresponding to a measurement data storage location of an entity sensor may be added to a namespace associated with measurement data to determine a node configured for the measurement data storage location of the entity sensor. For example, the configured node may be represented as: a namespace W (measurement data storage location W) indicates that there is a node corresponding to the measurement data storage location W, i.e., a storage location attribute node, in the namespace W contained in the modeling map space. That is, the storage location attribute node is a node corresponding to the measured data storage location of the entity device. At this point, a target storage attribute node may be generated for pointing to the storage location attribute node and the storage identification attribute node, the target storage attribute node may be regarded as a node configured for the entity attribute measurement data of the entity sensor, and the sensor node may point to the target storage attribute node. Alternatively, the relationship of edges between the target storage attribute node and the storage identification attribute node may be defined by a modeler, such as brick: hasTimeSeries Id indicates that the measurement data storage identifier is the data information corresponding to the storage identifier attribute node. The relationship of edges between the target storage attribute node and the storage location attribute node may be defined by a modeler, such as brick: the storedAt represents data information corresponding to the storage location attribute node as the measurement data storage location.
The attribute subordinate relation between the entity name of the entity sensor and the entity attribute measurement data of the entity sensor is used for indicating that measurement data related information of the entity sensor corresponding to the entity name is entity attribute measurement data, that is, measurement data related information of a sensor node (node a) corresponding to the entity name of the entity sensor is entity attribute measurement data corresponding to a second sensor attribute node (node D) of the entity sensor. For example, sensor attribute information (sensor attribute information B) configured for the physical sensor for the measurement data association information is used to indicate the relationship of the edge between the node a and the node D as: the brick is the entity attribute measurement data corresponding to the node D, and the measurement data related information of the entity sensor corresponding to the node A is represented by the brick. Thus, a node-pointing relationship between the sensor node and the second sensor attribute node may be constructed by the sensor attribute information B, that is, the node-pointing relationship is used to indicate that the second sensor attribute node is pointed to by the sensor node, and the relationship defined by the edge between the sensor node and the second sensor attribute node is determined based on the sensor attribute information B. Thus, the sensor instance of the business sensor may be updated by the second sensor attribute node, the node pointing relationship between the sensor node and the second sensor attribute node. The sensor instance may also be used to record a second sensor attribute node, a node pointing relationship between the sensor node and the second sensor attribute node. That is, in the updated sensor instance, the sensor node points to a second sensor attribute node that points to a storage identification attribute node and to a storage location attribute node.
Alternatively, it is also possible to determine the storage identification attribute node (node D1) and the storage location attribute node (node D2) as nodes configured for the entity attribute measurement data of the entity sensor. Thus, in the updated sensor instance, the storage identification attribute node is pointed to at the sensor node and the storage location attribute node is pointed to at the sensor node. The sensor attribute information B is used to indicate that the relationship of the edges between the node a and the node D1 is: brick: the relationship of the hasTimeSeries Id, the edges between node A and node D2 is: brick: the storedAt indicates that the measurement data associated information of the entity sensor corresponding to the node a is the entity attribute measurement data corresponding to the node D1 and the node D2. Therefore, a node-oriented relationship between the sensor node and the second sensor attribute node, that is, a node-oriented relationship indicating that the second sensor attribute node (node D1 and node D2) is oriented by the sensor node can be constructed by the sensor attribute information B, and the relationship defined by the edges between the sensor node and the second sensor attribute node (node D1 and node D2) is determined based on the sensor attribute information B.
For example, as shown in fig. 10, fig. 10 is a schematic diagram of a setup process of an example of a sensor according to an embodiment of the present application; s51, traversing and acquiring sensor metadata from service metadata; s52, determining whether the entity type of the entity sensor is the sensor type in the sensor metadata obtained through traversing; s53, if the entity type of the entity sensor is determined to be the sensor type (namely, the traversed metadata is sensor metadata at the moment), determining that the sensor type metadata of the equipment sensor exists in the service metadata; if it is determined that the entity type of the entity sensor is not the sensor type (i.e., the metadata traversed at this time is not the sensor metadata), it is determined that the sensor metadata of the device sensor does not exist in the service metadata, and step S51 is continuously executed; s54, acquiring entity names of entity sensors in the sensor metadata, and determining nodes configured for the entity names of the entity sensors as sensor nodes of the equipment sensors in a modeling mapping space; s55, acquiring an entity name space of an entity sensor in the sensor type metadata; s56, when the entity name space of the entity sensor belongs to the first name space, acquiring the entity attribute type of the entity sensor in the sensor class metadata, and determining the node configured for the entity attribute type of the entity sensor in the first name space as the sensor class node of the equipment sensor in the modeling mapping space; s57, when the entity name space of the entity sensor belongs to the second name space, acquiring the entity attribute type of the entity sensor in the sensor class metadata, and determining the node configured for the entity attribute type of the entity sensor in the second name space as a sensor class node of the entity attribute type in the modeling mapping space; s58, configuring sensor attribute information for the entity sensor based on the attribute subordinate relation between the entity name of the entity sensor and the entity attribute type of the entity sensor; s59, constructing a node pointing relationship between the sensor nodes and the sensor class nodes based on the configured sensor attribute information; s510, generating a sensor instance of the device sensor based on the node pointing relationship between the sensor node and the sensor class node; s511, acquiring an entity attribute measurement unit of an entity sensor in sensor metadata, and determining a node configured for the entity attribute measurement unit of the entity sensor as a first sensor attribute node of the equipment sensor in a modeling mapping space; s512, constructing a node pointing relationship between the sensor node and the first sensor attribute node based on the attribute subordinate relationship between the entity name of the entity sensor and the entity attribute measurement unit of the entity sensor; s513, updating a sensor instance of the device sensor based on the node pointing relationship between the sensor node and the first sensor attribute node; s514, acquiring entity attribute measurement data of an entity sensor in sensor metadata, and determining a node configured for the measurement data storage identification of the entity sensor as a storage identification attribute node of the equipment sensor in a modeling mapping space; s515, determining a node configured for the measured data storage position of the entity sensor as a storage position attribute node of the equipment sensor in the modeling mapping space; s516, generating a target storage attribute node for pointing to the storage identification attribute node and pointing to the storage location attribute node, and determining a node configured for the entity attribute measurement data of the entity sensor based on the target storage attribute node; s517, determining a node configured for the entity attribute measurement data of the entity sensor as a second sensor attribute node of the equipment sensor in the modeling mapping space; s518, constructing a node pointing relation between a sensor node and a second sensor attribute node based on the attribute subordinate relation between the entity name of the entity sensor and the entity attribute measurement data of the entity sensor; s519 updates a sensor instance of the device sensor based on the node pointing relationship between the sensor node and the second sensor attribute node.
As another example, as shown in fig. 11, fig. 11 is a schematic view of an establishment scenario of a sensor example provided by an embodiment of the present application; the sensor metadata comprises entity names, entity types, entity namespaces and entity attribute types of entity sensors mapped by the device sensors; determining a node configured for the entity name of the entity sensor as a sensor node 62 of the device sensor in the modeling map space 61; acquiring entity attribute types of the entity sensors in the sensor class metadata when the entity namespaces of the entity sensors belong to a first namespace (or a second namespace), and determining nodes configured for the entity attribute types of the entity sensors in the first namespace (or the second namespace) (collectively called a namespace 63) as sensor class nodes 64 of the device sensors in a modeling mapping space; configuring sensor attribute information 65 for the entity sensor based on an attribute membership between an entity name of the entity sensor and an entity attribute type of the entity sensor; a node orientation relation 66 between the sensor node and the sensor class node is constructed based on the sensor attribute information (the node orientation relation indicates that the sensor node points to the sensor class node, and the relation of edges between the sensor node and the sensor class node is a, a=rdf: type, a first type attribute connection relation (LK 1)), so as to establish a sensor instance in the modeling mapping space 61, where the establishing a sensor instance includes: sensor node 62, sensor class node 64 in namespace 63, node-directed relationship 66 between sensor node 62 and sensor class node 64.
Further, the sensor class metadata further includes an entity attribute measurement unit of the entity sensor; the node configured for the entity attribute measurement unit of the entity sensor may be determined as the first sensor attribute node 67 of the device sensor in the modeling mapping space, and the node pointing relationship 68 between the sensor node and the first sensor attribute node is constructed (the node pointing relationship indicates that the sensor node points to the first sensor attribute node, and the relationship of the edge between the sensor node and the first sensor attribute node is C, "C" is used to indicate that the measurement unit of the entity sensor corresponding to the sensor node is the entity attribute measurement unit indicated by the first sensor attribute node, and c=bridge: hasUnit, and the second type attribute connection relationship (LK 2)) to update the sensor instance in fig. 11, to obtain an updated sensor instance, where the updated sensor instance includes: sensor node 62, sensor class node 64 in namespace 63, node-directed relationship 66 between sensor node 62 and sensor class node 64, and node-directed relationship 68 between sensor node 62 and first sensor attribute node 67 are newly added.
Further, the sensor class metadata further includes entity attribute measurement data of the entity sensor; the node configured for the entity attribute measurement data of the entity sensor may be determined as the second sensor attribute node 69 of the device sensor in the modeling mapping space, and the node pointing relationship 610 between the sensor node and the second sensor attribute node is constructed (the node pointing relationship indicates that the sensor node points to the second sensor attribute node, and the relationship of the edge between the sensor node and the second sensor attribute node is D, "D" is used to indicate that the measurement data association information of the entity sensor corresponding to the sensor node is the entity attribute measurement data indicated by the second sensor attribute node, d=click: timings, and the third type attribute connection relationship (LK 3)) to update the sensor instance in fig. 11, to obtain an updated sensor instance, where the updated sensor instance includes: sensor node 62, sensor class node 64 in namespace 63, node-pointing relationship 66 between sensor node 62 and sensor class node 64, first sensor attribute node 67, and node-pointing relationship 68 between sensor node 62 and first sensor attribute node 67, and node-pointing relationship 610 between sensor node 62 and second sensor attribute node 69 are newly added. At this time, the second sensor attribute node 69 also points to the storage identifier attribute node 611 corresponding to the measurement data storage identifier (relationship of edges between nodes is E, e=bridge: hasTimeseriesId, fourth type attribute connection relationship (LK 4)), and to the storage location attribute node 612 corresponding to the measurement data storage location (relationship of edges between nodes is E, e=bridge: store, fifth type attribute connection relationship (LK 5)).
It will be appreciated that the data information included in the sensor metadata is not limited herein, and may include one or more data information in addition to the entity name, entity type, entity namespace, and entity attribute type of the entity sensor, which are exemplified herein only in terms of entity attribute measurement units and entity attribute measurement data. The corresponding nodes can be respectively configured based on the one or more data information to serve as sensor attribute nodes of the equipment sensor in the modeling mapping space, and the sensor instance is updated through the node pointing relationship between the sensor nodes and the sensor attribute nodes, so that the final complete sensor instance is obtained.
S204, based on the device subordination relation between the service device and the device sensor, configuring the device node in the device instance as a device master node, and configuring the sensor node in the sensor instance as a device child node subordinate to the device master node. The specific implementation of step S204 may be referred to the related description of the above embodiments, which is not repeated herein.
S205, modeling based on the equipment class node, the equipment main node, the sensor class node and the equipment sub-node to obtain a system modeling model of the service processing system.
The system modeling model is used for inquiring the device subordinate relation between the service device and the device sensor. It can be appreciated that the system modeling model may be used to record entity devices corresponding to service devices deployed in the service device system, and entity sensors corresponding to device sensors deployed in the service devices, and relationships between service devices and service devices (i.e., relationships between entity devices corresponding to service devices and entity devices corresponding to service devices), and relationships between service devices and device sensors (i.e., relationships between entity devices corresponding to service devices and entity sensors corresponding to device sensors). The system modeling model may be built according to the related description of the above embodiment.
For example, as shown in fig. 12 to 13, fig. 12 to 13 are schematic diagrams of a system modeling model building process according to an embodiment of the present application; the process for establishing the system modeling model comprises the following steps: s121, establishing a mapping relation between service equipment in a physical space and entity equipment in a modeling mapping space (metadata space), namely generating an equipment instance corresponding to the service equipment based on equipment metadata; s122, establishing a mapping relation between a device sensor of a physical space and an entity sensor of a modeling mapping space (metadata space), namely generating a sensor instance corresponding to the device sensor based on sensor metadata; s123, based on the device membership (topological connection relation, indicated by a dotted line in fig. 13) of the service device and the device sensor in the physical space, performing association (indicated by implementation in fig. 13) of the device instance and the sensor instance in the modeling mapping space, namely, associating the device node in the device instance with the sensor node in the sensor entity; s124, based on the service equipment and the equipment connection relation (topological connection relation, indicated by a dotted line in fig. 13) of the service equipment in a physical space, performing association (indicated by implementation in fig. 13) between the equipment instance and the equipment instance in a modeling mapping space, namely, associating the equipment node in the equipment instance with the equipment node in the equipment instance; s125, a system modeling model (such as a brick schema) is built through the device instance, the sensor instance, the relationship between the device instance and the sensor instance, and the relationship between the device instance and the device instance.
It can be understood that the technical scheme of the application can adopt the concept of the brick modeling when the system modeling is performed. brick is an open source data model and markup language that is intended to aid in the exchange and integration of data in the building and intelligent building fields. The structural definition of the brick dataset consists of a set of OWL (Ontology Web Language ) ontology files and RDF (Resource Description Framework ) data files for defining entities, properties and relationships in the building system. The click adopts an ontology-based method to describe entities and attributes (such as equipment nodes, equipment class nodes and the like) in the building system, and an RDF data model is used for representing the relations between the entities and the attributes (such as the relations between the equipment nodes and the equipment class nodes). brick also provides a generic set of namespaces and terms for describing various entities in a building system, such as sensors, devices, etc., i.e., the first namespaces and type terms in namespaces described above. These terms and namespaces may facilitate data exchange and integration between different building systems and devices. RDF, among other things, is a data model for describing and representing information resources on a network, which is based on a structure of triples, including subjects, predicates, and objects. The core idea of this model is to represent data by establishing relationships and properties between resources. RDF uniquely identifies and locates resources by using uniform resource identifiers (URIs, uniform Resource Identifier) to achieve uniqueness and accessibility worldwide. An advantage of this model is that semantic interoperability is facilitated, enabling different systems and applications to share, exchange, and understand the meaning of data. The flexibility and the expandability of RDF make it play an important role in the construction of semantic networks and knowledge graphs, and promote the communication of data and the discovery of knowledge. A connected network structure can be established through RDF to better organize, query, and infer knowledge about complex relationships between resources (i.e., relationships between business devices in a business processing system, etc.). RDF is also widely used in the building field, for example in Brick technology, which is a data model and standard for RDF-based building fields. Brick technology can utilize RDF capabilities to describe relationships between elements such as devices, sensors, etc. in a building, thereby supporting intelligent building management and energy efficiency optimization. Where OWL is a language used to build and represent an ontology. An ontology is a formalized model describing concepts, categories, attributes and relationships, used to represent the structuring and semantics of knowledge. OWL is based on RDF (Resource Description Framework), expands its expressive power, providing a richer semantic modeling and reasoning capability. It allows definition and organization of a conceptual hierarchy including relationships between classes (classes) and subclasses (subclasses). It also provides a definition of properties (properties) describing the association between classes and instances. OWL supports describing instances (instances) and relationships between instances so that knowledge can be represented in a more specific and concrete manner. OWL also provides a rich reasoning mechanism allowing logical reasoning, consistency checking and reasoning. The OWL becomes an important tool for constructing a semantic web and a knowledge graph, and supports automatic reasoning and semantic searching of data, so that a system modeling model of a business processing system can be constructed.
Therefore, the technical scheme of the application provides a quick modeling method of a system based on a brick model, which can greatly reduce the labor cost, the error probability and the modeling time of modeling. The method can automatically establish the mapping relation between the device sensor and the business device in the physical space and the entity sensor and the entity device in the metadata space. Meanwhile, by means of the standardized data entry template table and modeling logic codes, a modeler can efficiently complete the modeling step by only entering related information of service equipment and equipment sensors in the refrigerating system through the data entry template table, so that the modeling process is simplified, and the modeling efficiency and flexibility are improved. It will be appreciated that the modeling method may provide metadata formats (data entry template tables) for the refrigeration system based on the Brick concept to derive modeling metadata for modeling: modeling metadata is modeled through a semantic modeling method of Brick, and a system modeling model (metadata model) is obtained. Meanwhile, data can be rapidly queried through a system modeling model, and then an accurate and reliable open source measurement data set (the open source measurement data set is beneficial to improving data quality and reducing data access cost, so that training technology development of an AI algorithm and innovation of a data center industry are promoted) can be obtained, and related description of the measurement data set can be seen in related description of the following steps.
For example, as shown in fig. 14 to 16, fig. 14 to 16 are schematic diagrams of application scenarios of system modeling according to an embodiment of the present application; in an example of application of the embodiment of the application to a heating ventilation and air conditioning system (a refrigeration system), key equipment in the heating ventilation and air conditioning system can be modeled based on a brick semantic framework, a structural diagram of the key equipment in the heating ventilation and air conditioning system is shown in fig. 14, and connection relations among the key equipment are described in a dotted line frame shown in fig. 14, for example, the key equipment can comprise a refrigeration host, a chilled pump (chilled water pump), a cooling tower, a cold storage tank, a condenser, an evaporator and other equipment, and further comprises equipment such as an air conditioner, a rack and the like (wherein the cold channel temperature and the hot channel temperature exist), cooling water circulation exists between the condenser and the cooling tower, chilled water circulation exists between the evaporator and the cold storage tank, and cooling water outlet and chilled water outlet exist in the refrigeration host. It will be appreciated that different business devices (e.g., financial service devices) in a business system (e.g., financial system, data center system) may be cooled by a hvac system within the different business systems (e.g., financial system), and key devices in the hvac system for cooling the different business devices may be modeled, after which the system modeling may be used to perform device relationship analysis and the like for the hvac system in the financial system.
Wherein, refrigeration host computer: the refrigerating host is a core component of the heating ventilation air conditioning system, is responsible for refrigerating a refrigerant and providing refrigerating power, comprises point location parameters (namely measurement data of a sensor) such as an operating state, power, cooling side inlet and outlet water temperature, freezing side inlet and outlet water temperature, cooling side inlet and outlet water pressure, freezing side inlet and outlet water pressure, evaporator condenser temperature difference and the like, and is connected with a freezing pump, a cooling pump and a plate heat exchanger through pipelines.
Alternatively, a modeling relationship diagram between the refrigeration host and deployed device sensors (e.g., an operation state sensor 1 for measuring an operation state of the refrigeration host, a power sensor 2 for measuring a power of the refrigeration host, a cooling side inlet outlet water temperature sensor 3 for measuring a cooling side inlet outlet water temperature of the refrigeration host, a freezing side inlet outlet water temperature sensor 4 for measuring a cooling side inlet water pressure of the refrigeration host, a cooling side inlet outlet water pressure sensor 5 for measuring a cooling side inlet water pressure of the refrigeration host, a freezing side inlet water pressure sensor 6 for measuring a cooling side inlet water pressure of the refrigeration host, a temperature difference sensor 7 for measuring an evaporator condenser temperature difference of the refrigeration host) may be as shown in fig. 15.
The node corresponding to the entity name of the entity device corresponding to the refrigeration host is a device node a1 of the refrigeration host (the device node may display the entity name of the entity device corresponding to the cooling pump, such as "refrigeration host 01", and the device node may also display a unique identifier generated based on the namespace associated with the refrigeration host, where the unique identifier may be used to represent related information of the namespace associated with the refrigeration host and the entity name of the entity device corresponding to the refrigeration host, such as "datacenter// refrigeration host 01", where the node display form in the system modeling model is not limited), a device class node a2 in a device instance of the refrigeration host may be configured by the entity attribute type of the entity device corresponding to the refrigeration host (the device class node may display the entity attribute type of the entity device corresponding to the refrigeration host, such as "refrigeration host", and the device class node may also display a unique identifier generated based on the namespace associated with the entity attribute type, where the unique identifier may be used to represent related information of the namespace associated with the entity attribute type of the refrigeration host and the entity attribute type, such as "brk// entity type of the entity device corresponding to the entity type of the refrigeration host" brk "is configured as" brf 1", and the device class node 1 is pointed to a device class node 1". type (first type attribute connection relationship, LK 1).
In addition, the sensors 1 to 7 in the refrigeration host correspond to one sensor node (a 3 to a 9), respectively, and the sensor node may display thereon the entity names of the entity sensors corresponding to the corresponding device sensors, such as "operation state sensor 01", "power sensor 01", etc., and the sensor node may also display thereon a unique identifier generated based on the namespaces associated with the corresponding device sensors, which may be used to represent the related information of the namespaces associated with the corresponding device sensors and the entity names of the entity sensors corresponding to the corresponding device sensors, such as "datacenter// operation state sensor 01"; it will be understood that each of the entity sensors corresponding to the device sensors has an entity attribute measurement unit, that is, the entity sensors corresponding to the sensors 1 to 7 in the refrigeration host have an entity attribute measurement unit corresponding to one sensor attribute node, respectively, for example, the entity attribute measurement unit represented by the sensor attribute node a10 corresponding to the operation state sensor 1 is "no unit" (that is, the entity attribute measurement unit of the entity sensor corresponding to the operation state sensor 1 may be displayed on the sensor attribute node a10, for example, "no unit", and the unique identifier generated based on the naming space associated with the entity attribute measurement unit of the operation state sensor 1 may be displayed on the sensor attribute node, and the unique identifier may be used to represent the related information of the naming space associated with the entity attribute measurement unit and the entity attribute measurement unit of the entity sensor corresponding to the operation state sensor 1, for example, "unit// no unit", and the sensor node corresponding to the operation state sensor 1 points to the sensor attribute node a10, for example, "unit// no unit", and the relationship is brick: hasUnit (second type of connection attribute, 2)); the entity attribute measurement unit represented by the sensor attribute node a11 corresponding to the power sensor 2 is "kw" (that is, the entity attribute measurement unit of the entity sensor corresponding to the power sensor 2 may be displayed on the sensor attribute node a11, such as "kw", and the unique identifier generated based on the namespace associated with the entity attribute measurement unit of the power sensor 2 may also be displayed on the sensor attribute node a11, which may be used to represent the related information of the namespace associated with the entity attribute measurement unit and the entity attribute measurement unit of the entity sensor corresponding to the power sensor 2, such as "unit// kw", and the sensor node corresponding to the power sensor 2 is directed to the sensor attribute node a11, with the relationship of brick: hasUnit); the entity property measurement unit represented by the sensor property node a12 corresponding to the cooling side water outlet temperature sensor 3 is "degrees celsius" (that is, the entity property measurement unit of the entity sensor corresponding to the cooling side water outlet temperature sensor 3 may be displayed on the sensor property node a12, for example, "degrees celsius", and the unique identifier generated based on the namespace associated with the entity property measurement unit of the cooling side water outlet temperature sensor 3 may be displayed on the sensor property node a12, which may be used to represent the related information of the namespace associated with the entity property measurement unit and the entity property measurement unit of the entity sensor corresponding to the cooling side water outlet temperature sensor 3, for example, "unit// degree celsius", and the sensor node corresponding to the cooling side water outlet temperature sensor 3 is directed to the sensor property node a12, which is related to brick, hasUnit ". The entity property measurement unit represented by the sensor property node a12 corresponding to the freezing side water outlet temperature sensor 4 is" degrees celsius "(that is, the unique identifier may be displayed on the sensor node a12, for example, may be used to represent the related information of the entity property measurement unit corresponding to the entity property measurement unit of the entity side water outlet temperature sensor 3, for example," the entity property measurement unit corresponding to the cooling side water outlet temperature sensor 4 "may be displayed on the basis of the unique identifier, which may be displayed on the sensor property node a12, and the sensor node corresponding to the freezing side water inlet and outlet temperature sensor 4 points to the sensor attribute node a12, and the relation is brick, hasUnit; the entity property measurement unit represented by the sensor property node a13 corresponding to the cooling side water inlet and outlet pressure sensor 5 is "kilopascal" (that is, the entity property measurement unit of the entity sensor corresponding to the cooling side water inlet and outlet pressure sensor 5, such as "kilopascal", can be displayed on the sensor property node a13, and the unique identifier generated based on the namespace associated with the entity property measurement unit of the cooling side water inlet and outlet pressure sensor 5 can be displayed on the sensor property node a13, which can be used for representing the related information of the namespace associated with the entity property measurement unit and the entity property measurement unit of the entity sensor corresponding to the cooling side water inlet and outlet pressure sensor 5, such as "unit// kilopascal", and the sensor property node corresponding to the cooling side water inlet and outlet pressure sensor 5 points to the sensor property node a13, which is a brake, the entity property measurement unit represented by the freezing side water inlet and outlet pressure sensor 6 is "kilopascal" (that is, the unique identifier generated based on the entity property measurement unit corresponding to the entity property measurement unit of the entity corresponding to the cooling side water inlet and outlet pressure sensor 5, such as "unit of the entity property unit corresponding to the cooling side water inlet and outlet pressure sensor 6 can be displayed on the sensor property node a13, which can be used for representing the unique identifier associated with the entity property of the entity sensor corresponding to the entity sensor property unit corresponding to the cooling side water inlet and outlet pressure sensor 5, and the sensor node corresponding to the water inlet and outlet pressure sensor 6 at the freezing side points to the sensor attribute node a13, and the relationship is brick, hasUnit; the entity property measurement unit represented by the sensor property node a12 corresponding to the temperature difference sensor 7 is "degrees celsius" (that is, the entity property measurement unit of the entity sensor corresponding to the temperature difference sensor 7 may be displayed on the sensor property node a12, such as "degrees celsius", and the unique identifier generated based on the namespace associated with the entity property measurement unit of the temperature difference sensor 7 may also be displayed on the sensor property node a12, which may be used to represent the relevant information of the namespace associated with the entity property measurement unit and the entity property measurement unit of the entity sensor corresponding to the temperature difference sensor 7, such as "unit// degrees celsius", and the sensor node corresponding to the temperature difference sensor 7 is directed to the sensor property node a12, with the relationship of brick: halunit.
Further, it will be appreciated that there is a connection relationship between the appliance node a1 of the refrigeration host and the sensor nodes a3-a9 of the deployed appliance sensors, with the sensor nodes a3-a9 pointing to the appliance node a1, respectively, and the relationship being brick: isPointOf (first type of appliance connection relationship, LK 3).
Wherein, the cooling tower: the cooling tower is equipment for discharging the heat in the refrigeration host machine to the atmosphere in an evaporation mode through a fan, comprises point location parameters (namely measurement data of a sensor) such as inlet and outlet water temperature, running state, power, fan frequency and the like, and is connected with the refrigeration host machine, a cooling pump and a plate heat exchanger through pipelines.
Alternatively, a modeling relationship diagram between the cooling tower and deployed equipment sensors (such as a temperature sensor 1 for measuring the water inlet and outlet temperatures of the cooling tower, an operating state sensor 2 for measuring the operating state of the cooling tower, a power sensor 3 for measuring the power of the cooling tower, a fan frequency sensor 4 for measuring the fan frequency of the cooling tower) may be as shown in fig. 16.
The node corresponding to the entity name of the entity device corresponding to the cooling tower is a device node b1 of the cooling tower (the device node may display the entity name of the entity device corresponding to the cooling tower, such as "cooling tower 01", and may also display a unique identifier generated based on the namespace associated with the cooling tower, where the unique identifier may be used to represent related information of the namespace associated with the cooling tower and the entity name of the entity device corresponding to the cooling tower, such as "datacenter// cooling tower 01", where the node display form in the system modeling model is not limited), the device class node b2 in the device instance of the cooling tower may be configured by the entity attribute type of the entity device corresponding to the cooling tower (the device class node may display the entity attribute type of the entity device corresponding to the cooling tower, such as "cooling tower", and may also display the unique identifier generated based on the namespace associated with the entity attribute type, where the unique identifier may be used to represent related information of the namespace associated with the entity attribute type of the cooling tower and the entity attribute type of the cooling tower, such as "brk/" brk 1 "may be configured to be a device class node b2 of the device of the cooling tower, and the device class node b2 may be configured to be a device class node b of the device of the entity device corresponding to the cooling tower: type (first type attribute connection relationship, LK 1).
In addition, the sensors 1 to 4 in the cooling tower correspond to one sensor node (b 3 to b 6), respectively, and the sensor node may display thereon an entity name of the entity sensor corresponding to the corresponding device sensor, such as "temperature sensor 01", and may also display thereon a unique identifier generated based on the namespace associated with the corresponding device sensor, which may be used to represent related information of the namespace associated with the corresponding device sensor and the entity name of the entity sensor corresponding to the corresponding device sensor, such as "datacenter// temperature sensor 01"; it will be understood that each of the entity sensors corresponding to the device sensors has an entity attribute measurement unit, that is, each of the sensors 1 to 4 in the cooling tower has an entity attribute measurement unit corresponding to one of the sensor attribute nodes, respectively, such as the entity attribute measurement unit represented by the sensor attribute node b7 corresponding to the temperature sensor 1 is "celsius" (that is, the entity attribute measurement unit of the entity sensor corresponding to the temperature sensor 1 may be displayed on the sensor attribute node b7, such as "celsius", and the unique identifier generated based on the namespace associated with the entity attribute measurement unit of the temperature sensor 1 may be displayed on the sensor attribute node, which may be used to represent the related information of the namespace associated with the entity attribute measurement unit and the entity attribute measurement unit of the entity sensor corresponding to the temperature sensor 1, such as "unit// celsius", and the sensor node corresponding to the temperature sensor 1 is directed to the sensor attribute node b7, the relationship is a brick: hasunite (second type connection relationship, 2)); the entity attribute measurement unit represented by the sensor attribute node b8 corresponding to the operation state sensor 2 is "no unit" (that is, the entity attribute measurement unit of the entity sensor corresponding to the operation state sensor 2, such as "no unit", may be displayed on the sensor attribute node b8, and the unique identifier generated based on the namespace associated with the entity attribute measurement unit of the operation state sensor 2 may also be displayed on the sensor attribute node, which may be used to represent the relevant information of the namespace associated with the entity attribute measurement unit and the entity attribute measurement unit of the entity sensor corresponding to the operation state sensor 2, such as "unit// no unit", and the sensor node corresponding to the operation state sensor 2 points to the sensor attribute node b8, the relationship being a brick: hasUnit (second type attribute connection relationship, LK 2)); the entity attribute measurement unit represented by the sensor attribute node b9 corresponding to the power sensor 3 is "kilowatt" (that is, the entity attribute measurement unit of the entity sensor corresponding to the power sensor 3, such as "kilowatt", may be displayed on the sensor attribute node b9, and the unique identifier generated based on the name space associated with the entity attribute measurement unit of the power sensor 3 may be displayed on the sensor attribute node b9, which may be used to represent the relevant information of the name space associated with the entity attribute measurement unit and the entity attribute measurement unit of the entity sensor corresponding to the power sensor 3, such as "unit// kilowatt", and the sensor node corresponding to the power sensor 3 points to the sensor attribute node b9, the relationship is brick: hasUnit, and the entity attribute measurement unit represented by the entity attribute node b10 corresponding to the fan frequency sensor 4 is "hertz" (that is, on the sensor attribute node b10, which may be used to display the entity attribute measurement unit corresponding to the entity sensor 4, such as "hertz", and the entity attribute unit corresponding to the fan frequency sensor 4 may be displayed on the sensor attribute node b, which may be used to represent the name space associated with the entity attribute unit, and the entity attribute unit corresponding to the fan attribute unit 4, such as "unit" may be displayed on the sensor attribute node b 4 ".
Further, it will be appreciated that there is a connection relationship between the device node b1 of the cooling tower and the sensor nodes b3-b6 of the deployed device sensors, the sensor nodes b3-b6 being directed to the device node b1, respectively, and the relationship being brick: isPointOf (first type of device connection relationship, LK 3).
Wherein, the cooling pump: the cooling pump is responsible for delivering cooling water from the cooling tower to the heat exchanger of the refrigeration host to reduce the temperature of the refrigerant, comprises point location parameters (namely measurement data of the sensor) such as power, running state and frequency, and is connected with the refrigeration host, the cooling tower and the plate heat exchanger through pipelines.
Alternatively, a modeled relationship diagram between the cooling pump and deployed equipment sensors (e.g., power sensor 1 for measuring power of the cooling pump, running state sensor 2 for measuring running state of the cooling pump, frequency sensor 3 for measuring frequency of the cooling pump) may be as shown in fig. 17.
The node corresponding to the entity name of the entity device corresponding to the cooling pump is a device node c1 of the cooling pump (the device node may display the entity name of the entity device corresponding to the cooling pump, such as "cooling pump 01", and may also display a unique identifier generated based on the namespace associated with the cooling pump, where the unique identifier may be used to represent related information of the namespace associated with the cooling pump and the entity name of the entity device corresponding to the cooling pump, such as "datacenter// cooling pump 01", where the node display form in the system modeling model is not limited), the device class node c2 in the device instance of the cooling pump may be configured by the entity attribute type of the entity device corresponding to the cooling pump (the device class node may display the entity attribute type of the entity device corresponding to the cooling pump, such as "cooling pump", and may also display the unique identifier generated based on the namespace associated with the entity attribute type, where the unique identifier may be used to represent related information of the namespace associated with the entity attribute type of the cooling pump and the entity name corresponding to the entity type of the cooling pump, such as "brk/" brk 1 "may be displayed on the device class node, and the device class node c2 is pointed to the device class node 1 of the cooling pump/the device class node). type (first type attribute connection relationship, LK 1).
In addition, the sensors 1 to 3 in the cooling pump correspond to one sensor node (c 3 to c 5), respectively, and the sensor node may display thereon an entity name of the entity sensor corresponding to the corresponding device sensor, such as "power sensor 01", and may also display thereon a unique identifier generated based on the namespace associated with the corresponding device sensor, which may be used to represent related information of the namespace associated with the corresponding device sensor and the entity name of the entity sensor corresponding to the corresponding device sensor, such as "datacenter// power sensor 01"; it will be understood that each of the entity sensors corresponding to the plant sensors has an entity attribute measurement unit, that is, each of the entity sensors corresponding to the sensors 1 to 3 in the cooling pump has an entity attribute measurement unit corresponding to one of the sensor attribute nodes, respectively, such as the entity attribute measurement unit represented by the sensor attribute node c6 corresponding to the power sensor 1 is "kw" (that is, the entity attribute measurement unit of the entity sensor corresponding to the power sensor 1 may be displayed on the sensor attribute node c6, such as "kw", and the unique identifier generated based on the namespace associated with the entity attribute measurement unit of the power sensor 1 may be displayed on the sensor attribute node, and the unique identifier may be used to represent the related information of the namespace associated with the entity attribute measurement unit and the entity attribute measurement unit of the entity sensor corresponding to the power sensor 1, such as "unit// kw", and the sensor node corresponding to the power sensor attribute node c6 corresponding to the power sensor attribute node is pointed to the sensor attribute node c6, and the relationship is brick: hasUnit (second type connection relationship, 2)); the entity attribute measurement unit represented by the sensor attribute node c7 corresponding to the running state sensor 2 is "no unit" (that is, the entity attribute measurement unit of the entity sensor corresponding to the running state sensor 2 may be displayed on the sensor attribute node c7, for example, "no unit", and the unique identifier generated based on the namespace associated with the entity attribute measurement unit of the running state sensor 2 may be displayed on the sensor attribute node c8, which may be used to represent the relevant information of the namespace associated with the entity attribute measurement unit and the entity attribute measurement unit of the entity sensor corresponding to the running state sensor 2, for example, "unit// no unit", and the sensor node corresponding to the running state sensor 2 points to the sensor attribute node c7 in a relationship of brick: halunit, and the entity attribute measurement unit represented by the sensor attribute node c8 corresponding to the frequency sensor 3 is "hertz" (that is, for example, "the entity attribute measurement unit of the entity sensor corresponding to the frequency sensor 3 may be displayed on the sensor attribute node c8, which may be displayed based on the frequency unit, for example," the entity attribute unit corresponding to the frequency sensor unit 3 may be displayed on the sensor attribute node c, and the entity attribute unit corresponding to the sensor attribute unit corresponding to the frequency unit 3 may be displayed on the sensor attribute unit, which may be used to represent the unique attribute unit, and the entity attribute unit corresponding to the sensor attribute 3 may be displayed on the sensor attribute unit.
Further, it will be appreciated that there is a connection relationship between the equipment node c1 of the cooling pump and the sensor nodes c3-c5 of the deployed equipment sensors, with the sensor nodes c3-c5 pointing to the equipment node c1, respectively, and the relationship being brick: isPointOf (first type of equipment connection relationship, LK 3).
Wherein, the cryopump: the freezing pump is an important part for conveying chilled water from the refrigerating host to the air conditioner terminal equipment, comprises point location parameters (namely measurement data of a sensor) such as power, running state, frequency and the like, and is connected with the refrigerating host, the plate heat exchanger and the air conditioner terminal through pipelines.
Alternatively, a modeled relationship diagram between the cryopump and deployed plant sensors (e.g., power sensor 1 for measuring power of the cryopump, operating state sensor 2 for measuring operating state of the cryopump, frequency sensor 3 for measuring frequency of the cryopump) may be as shown in fig. 18.
The node corresponding to the entity name of the entity device corresponding to the cryopump is a device node d1 of the cryopump (the device node may display the entity name of the entity device corresponding to the cryopump, such as "cryopump 01", and may also display a unique identifier generated based on a namespace associated with the cryopump, where the unique identifier may be used to represent related information of the namespace associated with the cryopump and the entity name of the entity device corresponding to the cryopump, such as "datacenter// cryopump 01", where the node display form in the system modeling model is not limited), the device class node d2 in the device instance of the cryopump may be configured by the entity attribute type of the entity device corresponding to the cryopump (the device class node may display the entity attribute type of the entity device corresponding to the cryopump, such as "cryopump", and may also display the unique identifier generated based on the namespace associated with the entity attribute type, where the unique identifier may be used to represent related information of the namespace associated with the entity attribute type of the cryopump and the entity type of the pump, such as "brk/" brk 1 "indicates that the entity attribute of the device class node/" brk 2 "points to the device class node 1"). type (first type attribute connection relationship, LK 1).
In addition, the sensors 1 to 3 in the cryopump correspond to one sensor node (d 3 to d 5), respectively, and the sensor node may display thereon an entity name of the entity sensor corresponding to the corresponding device sensor, such as "power sensor 01", and may also display thereon a unique identifier generated based on the namespace associated with the corresponding device sensor, which may be used to represent related information of the namespace associated with the corresponding device sensor and an entity name of the entity sensor corresponding to the corresponding device sensor, such as "datacenter// power sensor 01"; it will be understood that each of the physical sensors corresponding to each of the plant sensors has a physical attribute measurement unit, that is, each of the physical sensors corresponding to the sensors 1 to 3 in the cryopump has a physical attribute measurement unit corresponding to one of the sensor attribute nodes, respectively, such as the physical attribute measurement unit of the physical sensor corresponding to the power sensor 1 represented by the sensor attribute node d6 is "kw" (that is, the physical attribute measurement unit of the physical sensor corresponding to the power sensor 1 may be displayed on the sensor attribute node d6, such as "kw", and the unique identifier generated based on the namespace associated with the physical attribute measurement unit of the power sensor 1 may be displayed on the sensor attribute node, which may be used to represent the related information of the namespace associated with the physical attribute measurement unit and the physical attribute measurement unit of the physical sensor corresponding to the power sensor 1, such as "unit// kw", and the sensor node corresponding to the power sensor attribute node d6 is indicated by the relationship of brick unit (second type connection attribute, 2)); the entity attribute measurement unit represented by the sensor attribute node d7 corresponding to the running state sensor 2 is "no unit" (that is, the entity attribute measurement unit of the entity sensor corresponding to the running state sensor 2 may be displayed on the sensor attribute node d7, for example, "no unit", and the unique identifier generated based on the namespace associated with the entity attribute measurement unit of the running state sensor 2 may be displayed on the sensor attribute node, which may be used to represent the relevant information of the namespace associated with the entity attribute measurement unit and the entity attribute measurement unit of the entity sensor corresponding to the running state sensor 2, for example, "unit// no unit", and the sensor node corresponding to the running state sensor 2 points to the sensor attribute node d7 in the relationship of brick: halunit, and the entity attribute measurement unit represented by the sensor attribute node d8 corresponding to the frequency sensor 3 may be displayed on the sensor attribute node d8, for example, "hertz" (that is, for example, "the entity attribute measurement unit corresponding to the entity sensor 3 may be displayed on the sensor attribute node 3, which may be displayed on the sensor attribute node based on the sensor attribute node, which may be displayed on the sensor attribute unit corresponding to the entity attribute unit, and the sensor attribute unit corresponding to the entity attribute unit 3 may be displayed on the sensor attribute unit, which may be displayed on the sensor attribute node corresponding to the sensor attribute unit 3, and the sensor attribute unit corresponding to the entity attribute unit 3.
Further, it will be appreciated that there is a connection between the device node d1 of the cryopump and the sensor nodes d3-d5 of the deployed device sensor, with the sensor nodes d3-d5 pointing to the device node d1, respectively, and the relationship being brick: isPointOf (first type of device connection, LK 3).
Wherein, plate heat exchanger: the plate heat exchanger is used for transmitting heat to air in a water conduction mode, plays a role in cooling, comprises point location parameters (namely measurement data of a sensor) such as water inlet and outlet temperature of a cooling side and water outlet temperature of a freezing side, and is connected with a refrigeration host, a freezing pump and a cooling pump through pipelines.
Alternatively, a modeling relationship diagram between the plate heat exchanger and deployed equipment sensors (e.g., a cooling side inlet water outlet temperature sensor 1 for measuring cooling side inlet water outlet temperature of the plate heat exchanger, a freezing side inlet water outlet temperature sensor 2 for measuring freezing side inlet water outlet temperature of the plate heat exchanger) may be as shown in fig. 19.
The node corresponding to the entity name of the entity device corresponding to the plate heat exchanger is a device node e1 of the plate heat exchanger (the device node may display the entity name of the entity device corresponding to the plate heat exchanger, such as "plate heat exchanger 01", and may also display a unique identifier generated based on a namespace associated with the plate heat exchanger, where the unique identifier may be used to represent related information of the namespace associated with the plate heat exchanger and the entity name of the entity device corresponding to the plate heat exchanger, such as "datacenter// plate heat exchanger 01", where the node display form in the system modeling model is not limited), a device class node e2 in a device instance of the plate heat exchanger may be configured by the entity attribute type of the entity device corresponding to the plate heat exchanger (the device class node may display the entity attribute type of the entity device corresponding to the plate heat exchanger, such as "plate heat exchanger", and the device class node may also display a unique identifier generated based on the namespace associated with the entity attribute type, where the unique identifier may be used to represent related information of the entity type associated with the plate heat exchanger, such as "brk// entity attribute type" brf, and the device class node 2 "may be configured to be the device class node 1": type (first type attribute connection relationship, LK 1).
In addition, the sensors 1-2 in the plate heat exchanger correspond to one sensor node (e 3-e 4), respectively, and the sensor node may display thereon an entity name of an entity sensor corresponding to the corresponding device sensor, such as "cooling side water outlet temperature sensor 01", and the sensor node may also display thereon a unique identifier generated based on a namespace associated with the corresponding device sensor, which may be used to represent information related to the namespace associated with the corresponding device sensor and an entity name of an entity sensor corresponding to the corresponding device sensor, such as "datacenter// cooling side water outlet temperature sensor 01"; it can be understood that each of the entity sensors corresponding to each of the equipment sensors has an entity attribute measurement unit, that is, the entity sensor corresponding to each of the sensors 1-3 in the plate heat exchanger has an entity attribute measurement unit corresponding to one of the sensor attribute nodes, for example, the entity attribute measurement unit represented by the sensor attribute node e5 corresponding to the cooling side water outlet temperature sensor 1 is "celsius" (that is, the entity attribute measurement unit of the entity sensor corresponding to the cooling side water outlet temperature sensor 1 may be displayed on the sensor attribute node e5, for example, "celsius"), and the unique identifier generated based on the naming space associated with the entity attribute measurement unit of the cooling side water outlet temperature sensor 1 may be displayed on the sensor attribute node, which may be used to represent the information related to the naming space associated with the entity attribute measurement unit and the entity attribute measurement unit of the entity sensor corresponding to the cooling side water outlet temperature sensor 1, for example, "unit// celsius", and the sensor node corresponding to the cooling side water outlet temperature sensor 1 may be displayed on the sensor attribute node e5, for example, as a first-class attribute relationship of the first-type attribute, and second attribute relationship of the first attribute, the second attribute, the first attribute, and second attribute, the second attribute, and third attribute, and fourth attribute; the entity attribute measurement unit represented by the sensor attribute node e5 corresponding to the freezing side water outlet temperature sensor 2 is "degrees celsius" (that is, the entity attribute measurement unit of the entity sensor corresponding to the freezing side water outlet temperature sensor 2, such as "degrees celsius", may be displayed on the sensor attribute node e5, and the unique identifier generated based on the namespace associated with the entity attribute measurement unit of the freezing side water outlet temperature sensor 2 may also be displayed on the sensor attribute node, which may be used to represent the relevant information of the namespace associated with the entity attribute measurement unit and the entity attribute measurement unit of the entity sensor corresponding to the freezing side water outlet temperature sensor 2, such as "unit// degrees celsius", and the sensor node corresponding to the freezing side water outlet temperature sensor 2 is directed to the sensor attribute node e5, with the relationship of brick: hasUnit.
Furthermore, it will be appreciated that the plate heat exchanger equipment node e1 has a connection relationship with the sensor nodes e3-e4 of the deployed equipment sensors, the sensor nodes e3-e4 being directed to the equipment node e1, respectively, and the relationship being brick: ispointon of (first type of equipment connection relationship, LK 3).
It will be appreciated that for the above various business devices, modeling can be performed using a click semantic framework, which enables fine-grained description of the business device by defining various entities, relationships, and attributes. For example, a refrigeration host is defined as a "refrigeration host" entity, while a cryopump and a cooling pump are defined as "cryopump" and "cooling pump" entities, respectively. The cooling tower is then defined as a "cooling tower" entity, while the plate heat exchanger is defined as a "plate heat exchanger" entity. Meanwhile, a relationship between service devices and service devices, and a relationship between service devices and device sensors are described. Therefore, through modeling of the brick semantic framework, the relationship and the effect among the devices of the heating ventilation and air conditioning system can be more comprehensively known. For example, the energy transfer relationship between the refrigeration host and the cooling pump, and the water flow transfer relationship between the cooling tower and the cooling pump, may be described by a relational orientation. And subsequently, the heating, ventilation and air conditioning system can be subjected to system optimization through a system modeling result. That is, the use of the brick semantic framework can make the relationship and function among the devices in the hvac system better understood, and provides more support for optimizing and debugging the system.
Taking the cooling pump and the refrigeration host as an example, taking the example of a part result of a brack modeling model of the heating ventilation air conditioning system (taking the example of a part sensor of the cooling pump and the deployment of the part sensor of the refrigeration host, and a relation between the cooling pump and the refrigeration host) as shown in fig. 20, for example, a device node 151 in a device instance of the cooling pump can be configured through a physical name of a physical device corresponding to the cooling pump (the device node can display the physical name of the physical device corresponding to the cooling pump, such as "cooling pump 01", and the device node can also display a unique identifier generated based on a naming space associated with the cooling pump, wherein the unique identifier can be used for representing related information of the naming space associated with the cooling pump and the physical name of the physical device corresponding to the cooling pump, such as "datacenter// cooling pump 01"); the device node 152 in the device instance of the refrigeration host may be configured by the entity name of the entity device corresponding to the refrigeration host (the device node may display thereon the entity name of the entity device corresponding to the refrigeration host, such as "refrigeration host 01", and may also display thereon a unique identifier generated based on the namespace associated with the refrigeration host, which may be used to represent related information of the namespace associated with the refrigeration host and the entity name of the entity device corresponding to the refrigeration host, such as "datacenter// refrigeration host 01"); the equipment class node 153 in the equipment instance of the cooling pump may be configured by the entity attribute type of the entity equipment corresponding to the cooling pump (the equipment class node may display the entity attribute type of the entity equipment corresponding to the cooling pump, such as "cooling pump", and may also display a unique identifier generated based on the namespace associated with the entity attribute type, the unique identifier may be used to represent related information of the namespace associated with the entity attribute type of the cooling pump and the entity attribute type of the entity equipment corresponding to the cooling pump, such as "brick// cooling pump"), the equipment node 151 points to the equipment class node 153, and the relationship is rdf: type (first type attribute connection relationship, LK 1); the device class node 154 in the device instance of the refrigeration host may be configured by the entity attribute type of the entity device corresponding to the refrigeration host (the device class node may display the entity attribute type of the entity device corresponding to the refrigeration host, such as "refrigeration host", and may also display a unique identifier generated based on the namespace associated with the entity attribute type, the unique identifier may be used to represent related information of the namespace associated with the entity attribute type of the refrigeration host and the entity attribute type of the entity device corresponding to the refrigeration host, such as "click// refrigeration host"), the device node 152 points to the device class node 154, and the relationship is rdf: type; the sensor node 155 in the sensor instance of the power measurement sensor may be configured by the entity name of the entity sensor corresponding to the power measurement sensor in the cooling pump (the sensor node may have displayed thereon the entity name of the entity sensor corresponding to the power measurement sensor, such as "power measurement sensor 01", and the sensor node may also have displayed thereon a unique identifier generated based on the namespace associated with the power measurement sensor, which may be used to represent information related to the namespace associated with the power measurement sensor and the entity name of the entity sensor corresponding to the power measurement sensor, such as "datacenter// power measurement sensor 01"); the sensor node 156 in the sensor instance of the cooling side in-take-out water temperature sensor may be configured by the entity name of the entity sensor corresponding to the cooling side in-take-out water temperature sensor in the refrigeration host (the sensor node may display thereon the entity name of the entity sensor corresponding to the cooling side in-take-out water temperature sensor, such as "cooling side in-take-out water temperature sensor 01", and the sensor node may also display thereon a unique identifier generated based on the namespace associated with the cooling side in-take-out water temperature sensor, which may be used to represent information about the namespace associated with the cooling side in-take-out water temperature sensor and the entity name of the entity sensor corresponding to the cooling side in-take-out water temperature sensor, such as "datacenter// cooling side in-take-out water temperature sensor 01"); a sensor attribute node 157 in the sensor instance of the cooling side water outlet temperature sensor may be configured by an entity attribute measurement unit of the entity sensor corresponding to the cooling side water outlet temperature sensor in the refrigeration host (the sensor attribute node may display thereon an entity attribute measurement unit of the entity sensor corresponding to the cooling side water outlet temperature sensor, such as "celsius", and the sensor attribute node may also display thereon a unique identifier generated based on a namespace associated with the entity attribute measurement unit of the cooling side water outlet temperature sensor, the unique identifier may be used to represent related information of the namespace associated with the entity attribute measurement unit and the entity attribute measurement unit of the entity sensor corresponding to the cooling side water outlet temperature sensor, such as "unit// celsius"), the sensor node 155 points to the sensor attribute node 157 and has a relationship of bridge: hasUnit (second type attribute connection relationship, LK 2); the sensor attribute node 158 in the sensor instance of the cooling pump may be configured by the entity attribute measurement units of the entity sensor corresponding to the power measurement sensor in the cooling pump (the sensor attribute node may have displayed thereon the entity attribute measurement units of the entity sensor corresponding to the cooling pump, such as "kw", and the sensor attribute node may also have displayed thereon a unique identifier generated based on the namespace associated with the entity attribute measurement unit of the cooling pump, the unique identifier may be used to represent information related to the namespace associated with the entity attribute measurement unit and the entity attribute measurement units of the entity sensor corresponding to the cooling pump, such as "unit// kw"), the sensor node 156 pointing to the sensor attribute node 158 and having the relationship brick: hasUnit; meanwhile, due to the device dependency relationship between the cooling pump and the power measurement sensor, a relationship (relationship being brick: isPointOf (first type device connection relationship, LK 3)) between the sensor node 155 corresponding to the power measurement sensor and the device node 151 corresponding to the cryopump is generated; because of the device dependency relationship between the refrigeration host and the cooling side inlet/outlet water temperature sensor, a relationship (relationship of brick: ispintof) is generated between the sensor node 156 corresponding to the cooling side inlet/outlet water temperature sensor pointing to the device node 152 in the device instance of the refrigeration host; because of the device connection relationship (i.e., water flow direction relationship, device upstream-downstream relationship) between the refrigeration host and the cooling pump, the relationship (relationship is brick. Feeds (LK 4)) between the device nodes 151 corresponding to the refrigeration pump and the device nodes 152 in the device instance of the refrigeration host is generated. It will be appreciated that the node display morphology in the click modeling model is not limited herein, and may be specifically defined by a modeler, which is merely an example herein.
The application architecture of system modeling is shown in fig. 21, where operation measurement data generated by device sensors in each service device in the service processing system is stored in a database 211, a system modeling model 213 (including, for example, device nodes, sensor nodes, and node pointing relationships between the device nodes and the sensor nodes) is obtained by performing system modeling on the service processing system 212, the operation measurement data can be indexed and queried in the database by the system modeling model to form a system measurement data set 214 (when the service processing system is a heating ventilation and air conditioning system, the system measurement data set is a trusted heating ventilation data set), and training of an AI algorithm can be performed by using the system measurement data; alternatively, anomaly detection and quality detection are performed on the system measurement data to obtain a target measurement data set 215 (target hvac data set), which may be processed into an open source measurement data set (open source hvac data set may include multiple open source trusted hvac data sets, such as data set a or data set B, and quality of different data sets may be evaluated by quality detection), which may be applied in academia and industry, such as training of AI models, and evaluation of AI models by related processing means. In addition, the credible power data set can be collected according to different business processing systems, and the capacity and cost analysis of the data center system can be carried out through different collected data sets.
It can be appreciated that the rapid modeling method provided by the embodiment of the application designs a standardized data entry template form and modeling logic codes. The modeler only needs to record the relevant information of the service processing system in the data entry template form, and the modeling logic code can automatically complete the system modeling process. The business Data table corresponding to the Data entry template table comprises entered table Data (tab Data), and the format of the business Data table can be excel (a table format), csv (a table format), pandas DataFrame (a table format) and the like. Illustratively, the information that the modeler needs to enter for the data entry template form is as follows: (1) For entity devices corresponding to service devices in a refrigeration system: for cooling devices (e.g., cooling towers, heat exchangers, refrigeration hosts, water pumps, etc.), the information that needs to be entered includes: entity name (name), the name of the entity device, for uniquely identifying the entity device; an entity type (class_type), a category of entities, such as "Equipment", indicated as device type; an entity name space (namespace), namely, the name space of entity equipment, wherein 'Brick' is selected if the name space is the name space in a Brick standard library, and corresponding naming is given if the name space is the user-defined name space, such as 'EXT'; entity attribute type (brick_type), specific type of entity device; notes), optional items such as some additional notes, are used to record other information of the entity device. (1) Entity sensor corresponding to device sensor of service device in refrigeration system: for device sensors in cooling devices (e.g., temperature sensors, power measurement sensors, etc.), the information that needs to be entered includes: entity name (name), the name of the entity sensor, for uniquely identifying the entity sensor; an entity type (class_type), a category of entities, such as "Sensor", indicated as Sensor type; an entity name space (namespace), wherein the name space of the entity sensor selects 'Brick' if the name space is in a Brick standard library, and gives corresponding names such as 'EXT' if the name space is a user-defined name space; entity attribute type (brick_type), specific type of entity sensor; entity attribute measurement unit (unit): a data unit of operation measurement data of the device sensor corresponding to the entity sensor; entity attribute storage identification (id): a data identifier in the database or data file for uniquely identifying operational measurement data of the device sensor in the database or data file; entity attribute storage location (db_location): a database or data file representing the stored operational measurement data, usable for quick locating and retrieving the operational measurement data; the device information (equivalent_tag set): related information corresponding to the service equipment to which the equipment sensor belongs, such as entity names of corresponding entity equipment; notes (notes), optional items such as some additional notes, are used to record other information of the physical sensor.
Among them, modeling logic code for system modeling is exemplified as follows:
(1) Acquiring service metadata:
metadata_df＝pd.read_csv('metadata_example.csv',index_col＝False)
reading business metadata "metadata_df" from a business data table "metadata_sample.csv";
(2) Establishment of device instance:
for index,row in metadata_df.iterrows():
sequentially traversing metadata from business metadata
row.str.strip()
Performing blank deletion processing on the traversed character string to obtain metadata
if row['class_type']＝＝'Equipment':
If the entity type "row [ 'class_type' ]" in the traversed metadata is the Equipment type "Equipment", the traversed metadata is the Equipment metadata, and the Equipment instance is built through the traversed metadata until all the Equipment metadata are traversed from the service metadata;
g.add((BLDG[row['name']],RDFS.label,Literal(row['name'])))
the expression of// BLDG [ row [ 'name' ] ] ] means that there is a row [ 'name' ] in the namespace defined by BLDG
The corresponding node, row ' name ' represents the entity name in the traversed device metadata, so as to be taken as a device node, and a device attribute label "Lireal (row ' name)", which is added to the device node "BLDG [ row ' name ' ]", is shown in RDFS.label, wherein the relationship between the device node and the device attribute label is that the device attribute label of the device node is "Lireal (row ' name ');
if row['namespace']＝＝'Brick':
If the entity name space in the traversed metadata is the first name space, establishing a node pointing relation between the equipment node and the equipment class node in the first name space;
g.add((BLDG[row['name']],A,BRICK[row['brick_type']]))
the method comprises the steps that// BRICK [ row [ 'BRICK_type' ] ] ] represents that a node corresponding to row [ 'BRICK_type' ] exists in a BRICK namespace (first namespace), row [ 'BRICK_type' ] represents an entity attribute type in traversed device metadata, so that the node is taken as a device class node, a node pointing relation between a device node BLDG [ row [ 'name' ] ] and the device class node BRICK [ row [ 'BRICK_type' ] ] ], the node pointing relation is A, and the A represents that the relationship between the device node and the device class node is "BRICK [ row [ 'BRICK_type' ] ]", which is indicated by the device class node, is provided by the device node;
elif row['namespace']＝＝'EXT':
if the entity name space in the traversed metadata is the second name space, establishing a node pointing relation between the equipment node and the equipment class node in the second name space;
g.add((BLDG[row['name']],A,EXT[row['brick_type']]))
the method includes the steps that// EXT [ row [ 'click_type' ] ] ] represents that a node corresponding to row [ 'click_type' ] exists in an extended naming space (second naming space), row [ 'click_type' ] represents an entity attribute type in traversed device metadata, so that the traversed entity attribute type is used as a device class node, a node pointing relation between a device node BLDG [ row [ 'name' ] ] and a device class node BRICK [ row [ 'click_type' ] ] ], the node pointing relation is A, the A represents that the relation between the device node and the device class node is "BRICK [ row [ 'click_type' ] ]", and the entity attribute type of the device node is "BRICK [ row [ 'click_type' ] ]", which is indicated by the device class node;
(3) Establishment of sensor examples:
for index,row in metadata_df.iterrows():
sequentially traversing metadata from business metadata
row.str.strip()
Performing blank deletion processing on the traversed character string to obtain metadata
if row['class_type']＝＝'Sensor':
If the entity type "row [ 'class_type' ]" in the traversed metadata is the Sensor type "Sensor", the traversed metadata is the Sensor metadata, and the Sensor instance is built through the traversed metadata until all the Sensor metadata are traversed from the service metadata;
g.add((BLDG[row['name']],RDFS.label,Literal(row['name'])))
the expression of// BLDG [ row [ 'name' ] ] ] means that there is a row [ 'name' ] in the namespace defined by BLDG
The corresponding node, row [ ' name ' ] represents the entity name in the traversed sensor metadata, so as to be taken as a sensor node, a sensor attribute label of Lireal (row [ ' name ' ] ") is added for the sensor node ' BLDG [ row [ ' name ' ] ]", RDFS.label represents that the relation between the equipment node and the sensor attribute label is that the sensor attribute label of the sensor node is Lireal (row [ ' name ' ] ";
if row['namespace']＝＝'Brick':
if the entity name space in the traversed metadata is the first name space, establishing a node pointing relation between the sensor node and the sensor class node in the first name space;
g.add((BLDG[row['name']],A,BRICK[row['brick_type']]))
The method includes the steps that// BRICK [ row [ 'BRICK_type' ] ] ] indicates that a node corresponding to row [ 'BRICK_type' ] exists in a BRICK namespace (first namespace), row [ 'BRICK_type' ] indicates an entity attribute type in traversed sensor metadata, the traversed sensor metadata is used as a sensor class node, a node pointing relation between a sensor node BLDG [ row [ 'name' ] ] and the sensor class node BRICK [ row [ 'BRICK_type' ] ] ], the node pointing relation is A, A indicates that the relation between the sensor node and the sensor class node is "BRICK [ row [ 'BRICK_type' ] ]", which is indicated by the sensor class node, and the relation between the sensor node and the sensor class node is the entity attribute type which the sensor node has;
elif row['namespace']＝＝'EXT':
if the entity name space in the traversed metadata is the second name space, establishing a node pointing relation between the sensor node and the sensor class node in the second name space;
g.add((BLDG[row['name']],A,EXT[row['brick_type']]))
the method includes the steps that// EXT [ row [ 'bridge_type' ] ] ] represents that a node corresponding to row [ 'bridge_type' ] exists in an extension naming space (second naming space), row [ 'bridge_type' ] represents an entity attribute type in traversed sensor metadata, the traversed entity attribute type is taken as a sensor class node, a node pointing relation between a sensor node BLDG [ row [ 'name' ] ] and a sensor class node BRICK [ row [ 'bridge_type' ] ] ], the node pointing relation is A, the relation between the sensor node and the sensor class node is A, and the entity attribute type of the sensor node is BRICK [ row 'bridge_type' ] ] "indicated by the sensor class node;
g.add((BLDG[row['name']],BRICK['hasUnit'],UNIT[row['unit']]))
The method comprises the steps that// UNIT [ row [ ' UNIT ' ] ] indicates that a node corresponding to row [ ' UNIT ' ] exists in a name space defined by the UNIT, row [ ' UNIT ' ] indicates an entity attribute measurement UNIT in traversed sensor metadata, so that the node pointing relationship between a sensor node BLDG [ row [ ' name ' ] ] and a first sensor attribute node UNIT [ row [ ' UNIT ' ] ], the node pointing relationship is BRICK [ ' hasUnit ' ], BRICK [ ' hasUnit ' ] indicates that the relationship between the sensor node and the first sensor attribute node is the measurement UNIT indicated by the first sensor attribute node ' UNIT [ row [ ' UNIT ' ] ];
timeseries_props＝
[(BRICK['hasTimeseriesId'],Literal(row['point'])),(BRICK['storedAt'],Literal(row['db_location']))]
the/(Literal (row [ 'Point' ]) representation identifies configured nodes for measurement data storage in traversed-to sensor metadata, i.e., storage identification attribute nodes; literal (row [ 'db_location' ]) represents the node configured for the measured data storage location in the traversed sensor metadata, i.e., the storage location attribute node; timeeries_tips represents a target storage attribute node for pointing to a storage identification attribute node and a storage location attribute node; the node pointing relation between the target storage attribute node and the storage identification attribute node is BRICK [ 'hasTimeSeries Id' ], which means that the relation between the target storage attribute node and the storage identification attribute node is that the measured data storage identification of the target storage attribute node is "real (row [ 'point' ]") indicated by the storage identification attribute node; the node pointing relationship between the target storage attribute node and the storage location attribute node is BRICK [ 'storedAt' ], which indicates that the relationship between the target storage attribute node and the storage location attribute node is a storage location indicated by a storage location attribute node "real (row) [ 'point' ]";
g.add((BLDG[row['name']],BRICK['timeseries'],timeseries_props))
Establishing a node pointing relation between a sensor node BLDG [ row [ 'name' ] ] and a target storage attribute node timelines_tips, wherein the node pointing relation is BRICK [ 'timelines' ], and the relation between the sensor node and the target storage attribute node is that the measured data association information of the sensor node is entity attribute measured data (measured data storage identification and measured data storage position) indicated by the target storage attribute node timelines_tips
(3) Association of device instance with sensor instance:
g.add((BLDG[row['name']],BRICK['isPointOf'],
BLDG[row['equipment_tagset']]))
the// BLDG [ row [ 'equivalent_tagset' ] ] ] indicates that there is a node corresponding to [ row [ 'equivalent_tagset' ] ] in the namespace defined by the BLDG; the [ row [ 'equivalent_tag set' ] ] ] represents the information of the equipment belonging to the traversed sensor metadata, and the node corresponding to the BLDG [ row [ 'equivalent_tag set' ] ] is the equipment node of the business equipment belonging to the equipment sensor because the information of the equipment belonging to the equipment is the same as the entity name of the entity equipment corresponding to the business equipment belonging to the equipment sensor; establishing a node pointing relation between a sensor node BLDG [ row [ 'name' ] ] and a BLDG [ row [ 'equivalent_tag set' ] ] node, wherein the node pointing relation is BRICK [ 'ispPoint of' ], and the relation between the sensor node and the BLDG [ row [ 'equivalent_tag set' ] node is represented as entity equipment indicated by the BLDG [ row [ 'equivalent_tag set' ] ] node;
(4) Association of device instance with device instance:
g.add((BLDG['Cooling_Tower_01'],Brick.feeds,BLDG['Condenser_Water_Pu mp_01']))
the// BLDG [ 'cooling_tower_01' ] indicates that there is a node 1 (a device node corresponding to an entity device of one service device) corresponding to the 'cooling_tower_01' in the namespace defined by the BLDG; BLDG [ 'concentrator_water_pump_01' ]) means that there is a node 2 (a device node corresponding to an entity device of one service device) corresponding to 'concentrator_water_pump_01' in the namespace defined by the BLDG; establishing a node pointing relationship between the node 1 and the node 2, wherein the node pointing relationship is Brick.feeds, and the downstream equipment, which indicates that the relationship between the node 1 and the node 2 is the entity equipment corresponding to the node 1, is the entity equipment corresponding to the node 2;
(5) Establishing a system modeling model:
g.serialize(f"./{output_filename}.ttl",format＝"ttl")
and integrating (e.g. serializing) all the generated information to obtain a system modeling model, and outputting the system modeling model in a ttl format file with an output file name of 'output_filename'.
It can be understood that the established system modeling model (Brick Schema) is a metadata model for a service processing system (such as a refrigerating system), and the Brick Schema is based on RDF and OWL technologies and uses a semantic modeling method, so that the semantic modeling method can more accurately describe objects such as equipment and sensors in the service processing system, make the semantics of data clearer and more definite, and is beneficial to the integration and application of the data. The key advantages of the brick modeling technology are that semantic modeling, expandability, openness, easiness in use and suitability for various application scenes are supported, and a more accurate, efficient and reliable metadata model can be provided for related systems. Subsequently, the Brick scheme can be introduced into the collection of a system measurement data set of the refrigerating system, so that related service personnel can conveniently and rapidly inquire data, or the relationship between the equipment sensor and the service equipment, the relationship between the service equipment and the like are analyzed. And meanwhile, the standardized advantage of the Brick scheme can ensure the mobility of the AI algorithm, such as migrating the trained AI algorithm from the simulation system to the service processing system in the physical space.
S206, when a data query request sent by a business object for a device sensor in the business processing system is obtained, a measurement data sequence of the device sensor indicated by the data query request is queried based on a system modeling model so as to determine a system measurement data set of the business processing system.
It can be appreciated that the system modeling model includes storage identity attribute nodes that are subordinate to the device sub-nodes corresponding to the device sensors, the storage identity attribute nodes being subordinate to the storage identity attribute nodes and subordinate to the storage location attribute nodes; the storage position attribute node is used for indicating a storage position corresponding to the operation measurement data of the device sensor, and the storage position attribute node is used for indicating a storage identification of the operation measurement data of the device sensor in the storage position. Thus, the system modeling model may be used for data queries. The data query process may be: when a data query request sent by a business object aiming at a device sensor in a business processing system is obtained, a storage identification attribute node and a storage position attribute node associated with the device sensor are obtained based on a system modeling model query, and a storage identification indicated by the storage identification attribute node and a storage position indicated by the storage position attribute node are obtained; the data query request is used for indicating a measurement data sequence matched with the query device sensor in the device operation period; positioning operation measurement data of the equipment sensor based on the storage identifier and the storage position, and acquiring a measurement data sequence matched with the equipment operation time period of the equipment sensor from the positioned operation measurement data of the equipment sensor; the sequence of measurement data is determined from operational measurement data obtained by the device sensor during the device operational period; and returning the measurement data sequence of the equipment sensor to the service terminal corresponding to the service object so that the service terminal determines a system measurement data set of the service processing system based on the operation measurement data in the measurement data sequence. That is, the operation measurement data generated by the device sensor in the designated device operation period can be quickly indexed through the system modeling model, and a measurement data sequence formed by the queried operation measurement data is used as a system measurement data set of the service processing system. Thus, the system measurement dataset may include measurement data sequences that all device sensors in the business processing system match over a device operational period. The acquired system measurement data set may be used for system analysis of the business processing system, creation of a simulation system, training of AI algorithms, and the like.
Furthermore, the system measurement data set can be subjected to abnormality detection and quality detection, so that the data processing of the system measurement data set is realized. For example, an anomaly detection condition for performing anomaly detection on the system measurement data set is obtained, and data anomaly detection is performed on the system measurement data set based on the anomaly detection condition to obtain a data anomaly detection result; if the data abnormality detection result indicates that the system measurement data set has operation measurement data meeting the abnormality detection condition, the operation measurement data meeting the abnormality detection condition is used as the abnormality measurement data; removing the abnormal measurement data from the measurement data set, and taking the measurement data set from which the abnormal measurement data is removed as a target measurement data set; and carrying out data integrity detection on the target measurement data set based on the measurement data set to obtain a data integrity detection result of the target measurement data set, determining data set quality information of the target measurement data set based on the data integrity detection result of the target measurement data set, and returning the data set quality information to a service terminal corresponding to the service object. The abnormal measurement data may be marked in the measurement dataset and the marked operational measurement data removed from the measurement dataset.
It is understood that determining the data integrity detection result of the target measurement data set may be determining the number of operation measurement data included in the system measurement data set and the number of operation measurement data included in the target measurement data set, and taking a ratio between the number of operation measurement data included in the target measurement data set and the number of operation measurement data included in the system measurement data set as the data integrity detection result. The data set quality value corresponding to the data integrity detection result can be determined based on the association relation between the data integrity detection result and the data set quality value, and the data integrity detection result and the corresponding data set quality value can be used as data set quality information and a target measurement data set to be returned to the service object. It will be appreciated that the quality of the target measurement dataset may be determined by the dataset quality information to determine whether training of the AI algorithm is to be performed with the target measurement dataset. This allows the selection of high quality measurement data sets to train the AI algorithm to provide the application effect of the measurement data sets. Meanwhile, the system measurement data set (or the target measurement data set) and the system modeling model can be externally provided as an open source data set, and related business application can be carried out by different users based on the open source data set and the system modeling model. That is, the abnormal measurement data may be removed from the operation measurement data corresponding to each point (sensor) in the system measurement data set, so as to perform quality evaluation to obtain the data integrity of the system measurement data set. It will be appreciated that this data integrity reflects the degree to which the system measures missing data in the dataset, and that a higher data integrity indicates less missing data and higher data quality. By evaluating the data integrity, the relevant business personnel can rapidly judge the availability of the processed target measurement data set and conveniently compare the quality of different target measurement data sets.
It will be appreciated that the system measurement data set includes multiple sets of operational measurement data obtained by the device sensor at a plurality of device operational moments over a device operational period; one device runtime corresponds to a set of operational measurement data. The system measurement data set may include a plurality of sets of operation measurement data obtained by a plurality of device sensors at a plurality of device operation times within a device operation period, respectively, and the process of performing abnormality detection for the operation measurement data of each device sensor is the same, and here, an abnormality detection process of the operation measurement data of one device sensor is described as an example. Acquiring an abnormality detection condition for detecting abnormality of the system measurement data set, performing data abnormality detection of the system measurement data set based on the abnormality detection condition, wherein the obtained data abnormality detection result may be that a measurement data abnormality range corresponding to the operation measurement data is acquired, and determining an abnormality detection condition based on the measurement data abnormality range; if the reference operation measurement data in the plurality of groups of operation measurement data belongs to the measurement data abnormal range based on the abnormal detection conditions, the reference operation measurement data is determined to meet the abnormal detection conditions, and a data abnormal detection result is obtained based on the reference operation measurement data. The data anomaly detection result is used to indicate that the reference operational measurement data is anomalous measurement data in the system measurement dataset.
Wherein the set of operational measurement data may comprise one operational measurement data. For example, the device sensor is used to measure temperature data, and a temperature data is then available at a device runtime. The abnormal range of the measured data corresponding to the operation measured data is an abnormal range aiming at the temperature data. When certain temperature data (reference operation measurement data) in the plurality of sets of operation measurement data belongs to the measurement data abnormality range, it is indicated that the reference operation measurement data satisfies the abnormality detection condition.
For example, the system measurement data set includes operation measurement data 1-4 (such as 10, 12, 14, 15 in sequence) obtained by the device sensor at device operation time 1-4 in the device operation period, and when the measurement data anomaly range (such as a range greater than 14 and less than 11) of the device sensor for the operation measurement data is obtained, it is determined that the operation measurement data 1 and the operation measurement data 5 are in the measurement data anomaly range, and the operation measurement data 1 and the operation measurement data 5 are determined as anomaly measurement data.
Wherein the set of operational measurement data may comprise a plurality of operational measurement data. For example, the device sensor is used to measure both temperature data and power data, and then one temperature data and one power data can be obtained at one device operation time. The abnormal range of the measured data corresponding to the operation measured data is an abnormal range 1 for the temperature data and an abnormal range 2 for the power data. When a certain temperature data (reference operation measurement data 1) among the plurality of sets of operation measurement data belongs to the measurement data abnormality range (i.e., abnormality range 1) associated with the reference operation measurement data 1, it is indicated that the reference operation measurement data 1 satisfies the abnormality detection condition. Similarly, when a certain power data (reference operation measurement data 2) among the plurality of sets of operation measurement data belongs to the measurement data abnormality range (i.e., abnormality range 2) associated with the reference operation measurement data 2, it is indicated that the reference operation measurement data 2 satisfies the abnormality detection condition.
For example, the system measurement data set includes first operation measurement data 1-4 (such as 10, 12, 14, 15 in order) and second operation measurement data 1-4 (such as 20, 22, 24, 25 in order) obtained by the device sensor at device operation times 1-4 in the device operation period, a measurement data anomaly range 1 (such as a range greater than 14 and less than 11) of the first operation measurement data by the device sensor is obtained, and a measurement data anomaly range 2 (such as a range greater than 24 and less than 21) of the second operation measurement data by the device sensor is obtained, then it is determined that the first operation measurement data 1 and the first operation measurement data 5 are in the measurement data anomaly range, and it is determined that the second operation measurement data 1 and the second operation measurement data 5 are in the measurement data anomaly range, and the first operation measurement data 1, the first operation measurement data 5, the second operation measurement data 1 and the second operation measurement data 5 are determined as anomaly measurement data.
It will be appreciated that the range of measurement data anomalies corresponding to the associated operational measurement data will vary from device sensor to device sensor, and may be specifically set by the relevant service personnel. Alternatively, the abnormal measurement data may be statistically determined from a plurality of sets of operation measurement data. The method of 3-sigma (a mathematical statistical method) may specifically be that normal distribution of operation measurement data of the device sensor is determined by a plurality of sets of operation measurement data, average measurement data corresponding to the plurality of sets of operation measurement data is determined by the normal distribution, deviation from the average measurement data in the plurality of sets of operation measurement data exceeds three times of standard deviation of the operation measurement data, and the determined operation measurement data is abnormal measurement data. Or, the abnormal measurement data can be determined from the multiple sets of operation measurement data by a physical method, for example, by a heat balance method, specifically, the multiple sets of operation measurement data are input into a heat balance calculation model, the heat balance calculation model is used for calculating the heat balance data of the service processing system in the equipment operation period through the multiple sets of operation measurement data, and the pre-trained heat balance calculation model is used for predicting and outputting the abnormal measurement data from the multiple sets of operation measurement data through the heat balance data. The detection method of the abnormal measurement data is not limited herein.
For example, as shown in fig. 22, fig. 22 is a schematic view of a data set construction scenario provided in an embodiment of the present application; the method for establishing the system measurement data set of the refrigerating system based on the Brick model is provided; the method comprises the steps of obtaining a service data table (namely design data provided by a constructor), obtaining service metadata (namely modeling metadata) from the service data table, performing system modeling through the modeling metadata to obtain a system modeling model of the refrigerating system, searching operation measurement data of equipment sensors in the refrigerating system through a system modeling model index to serve as an original system measurement data set (the original system measurement data set and the system modeling model can be provided as an open source system data set), further preprocessing the original system measurement data, such as anomaly detection, to obtain a target measurement data set after the anomaly measurement data is removed, performing data integrity detection on the target measurement data set to obtain data set quality information of the target measurement data set through the data integrity of the target measurement data set, and providing the target measurement data set, the system modeling model and the data set quality information together as the open source system data set.
Optionally, when the open source system data set is provided externally, the effective range related to the operation measurement data may also be provided together. It can be understood that the effective range can measure whether the operation measurement data is effective, for example, the effectiveness and the availability of the open source system data set in practical application can be ensured, the aspects of accuracy, completeness, consistency, timeliness and the like of the open source system data set can be considered, inaccurate, incomplete or outdated data used by a user of the data set can be avoided, and therefore the quality and the accuracy of subsequent data analysis are improved. In a refrigeration system, the range validity of operation measurement data is one of the important factors for ensuring the system data to be normal. In collecting, processing and using operational measurement data of a refrigeration system, it is necessary to ensure the accuracy and integrity of the operational measurement data and to ensure that the operational measurement data is within reasonable limits. For example, the collected raw system measurement data set can be subjected to abnormal data detection through the effective range of the running measurement data. The operational measurement data should be compatible with the operating conditions and environmental conditions of the refrigeration system. For example, the data such as temperature, pressure, flow rate should be matched to the operating requirements of the system, and the influence of environmental temperature, humidity and other factors should be considered. The method and accuracy of the acquisition and processing of operational measurement data need to be considered. The sensors and meters that collect operational measurement data should meet relevant standards and require periodic inspection and calibration. The transmission and processing of the operational measurement data also needs to be guaranteed error-free and loss-free. The effective range of the operation measurement data can be adjusted according to practical situations, for example, the effective range can be:
/>
In addition, when providing an open source system dataset, effective constraint information for the refrigeration system may also be provided. The validity is constrained. In refrigeration systems, effective constraint information is one of the important factors to ensure that the system is functioning properly. When using an open source system dataset, it is necessary to ensure that the data meets the operating requirements of the system and certain requirements and limitations of the system should be taken into account. For example, when the simulation system is built and operated through the open source system data set, the simulation system can be subjected to data constraint through effective constraint information, so that the operation scene of the simulation system is ensured to be closer to a real refrigeration system. When efficient analysis and use by an open source system dataset is required, specific requirements and limitations of the refrigeration system should be considered and accuracy and reliability of analysis results need to be ensured. Ensuring the constraint validity of the open source system data set requires comprehensive consideration of various factors and scientific and reasonable methods for using the data. For example, the following is defined effective constraint information: 1. cooling tower outlet water temperature (low) threshold limit; 2. the temperature of the water outlet (medium) of the cooling tower is limited by the temperature difference of the water inlet and outlet of the cooling side of the cooling machine; 3. minimum flow restriction on the chiller cooling side; 4. the outlet water temperature (higher) of the cooling tower is limited by the temperature difference of the inlet water and the outlet water of the cooling side of the cooling machine; 5. the temperature difference between the cooling side and the water inlet of the refrigeration host is limited by a high threshold value; 6. regulating and protecting a differential pressure bypass valve of a main cooling water pipe; 7. regulating and protecting a pressure difference bypass valve of a main chilled water pipe; 8. a cooling tower outlet water temperature (lower) threshold limit; 9. a cooling tower outlet water temperature (high) threshold limit; 10. and the outlet water temperature at the freezing side of the refrigeration host is limited by a high threshold value. These constraint information can be added together to the open source system dataset for application by the user.
It can be understood that the open source system data set is operation measurement data of the refrigeration system after cleaning and desensitizing (i.e. operation measurement data after abnormality detection), which includes key operation measurement data of device sensors in each service device, and also describes a physical network topology relationship between service devices. It can be understood that the open source system data set of the refrigeration system may refer to data collected by the refrigeration system of the data center, where the refrigeration system includes a refrigeration host, a cooling tower, a cooling pump, a freezing pump, and other devices, which are used to reduce the temperature of a machine room of the data center system and ensure the normal operation of server equipment. The open source system data set provides complete operation measurement data, including parameter information such as operation measurement data of a temperature sensor, operation measurement data of a humidity sensor, operation measurement data of an air pressure sensor and the like, and information such as working states of each service device (such as related attribute information of the service device and related attribute information of a device sensor) and the like, so that the open source system data set can help to be used for deeply understanding energy consumption characteristics and optimization strategies of the refrigeration system. Meanwhile, the open source system data set also comprises equipment topological relations, such as connection relations among all service equipment, so that communication flow and energy transfer among the service equipment can be analyzed, and the open source system data set can be used for better understanding of operation mechanisms, flow characteristics and energy scheduling of the refrigerating system. The open source system data set can be used for data analysis and system modeling, so that support can be provided for energy management and energy conservation and emission reduction of a data center system. The open source system data set can be used for researching the energy utilization efficiency, energy conservation, emission reduction, reliability verification and the like of the data center system under the operation of the refrigerating system, and has important significance for the design and operation of the data center system.
Therefore, the technical scheme of the application provides a method for generating the open source system data set applicable to the refrigerating system, and the method can generate the standardized open source system data set and can be used for developing and comparing different AI energy-saving algorithms. And providing a metadata format (data entry template table) for the refrigeration system based on a Brick model, wherein the metadata format can enable topological relations among service devices, service devices and device sensors to be read from service metadata in a machine-readable (RDF format) mode, and therefore the established open source system data set can be standardized and easy to use. Meanwhile, a quick modeling method of the brick model is provided, so that modeling efficiency can be improved, and modeling cost and error rate can be reduced. In addition, the generation of an open source system data set can be realized through a system modeling model, anomaly detection, quality detection and other processes, and the quality of the data set of different system measurement data can be evaluated, so that the development process of the system measurement data can be standardized, the generated system measurement data set is ensured to have high accuracy, high quality and high availability, and the high-quality open source system data set is provided for a user.
In the embodiment of the application, the service metadata for carrying out system modeling can be acquired from the service data table associated with the service processing system, and when the equipment type metadata of the service equipment exists in the service metadata, the equipment instance of the service equipment is established based on the equipment type metadata, and the equipment instance is used for recording the equipment type nodes of the service equipment in the service processing system and the equipment nodes for pointing to the equipment type nodes; the device instance can be automatically constructed based on the device metadata, so that the service device is mapped from a physical space to a modeling mapping space, namely, the service device which is actually present is subjected to data structuring, so that the datamation entity device corresponding to the service device is obtained, and the data space (digital space) where the entity device is located is the modeling mapping space; similarly, when the sensor class metadata of the device sensors deployed on the service equipment exist in the service metadata, a sensor instance of the device sensors is established based on the sensor class metadata, wherein the sensor instance is used for recording sensor class nodes of the device sensors in the service equipment and the sensor nodes pointing to the sensor class nodes; in this way, the automatic construction of the sensor instance can be performed based on the sensor metadata so as to map the equipment sensor from the physical space to the modeling mapping space, namely, the data structure of the equipment sensor which exists truly is realized so as to obtain the entity sensor which corresponds to the equipment sensor and has the data; in addition, the device node in the device instance can be configured as a device master node based on the device subordinate relation (such as recorded in a service data table) between the service device and the device sensor, and the sensor node in the sensor instance is configured as a device child node for pointing to the device master node, so that the association between the entity device and the entity sensor is automatically performed in the modeling mapping space, and the service device, the device sensor and the device subordinate relation between the service device and the device sensor in the service processing system can be digitally represented based on the system modeling model obtained by modeling the device class node, the device master node, the sensor class node and the device child node; it can be understood that a modeler can realize system modeling of the service processing system only by providing the service data table without performing a great deal of complicated operations, so that the system modeling process of the service processing system can be optimized, the complexity and difficulty of the whole system modeling process are reduced, and the system modeling efficiency and modeling convenience for the service processing system are further improved.
Further, referring to fig. 23, fig. 23 is a schematic structural diagram of a system data processing apparatus according to an embodiment of the present application. As shown in fig. 23, the system data processing apparatus 1 is applicable to a computer device. It should be understood that the system data processing apparatus 1 may be a computer program (comprising program code) running in a computer device, for example the system data processing apparatus 1 may be an application software; it will be appreciated that the system data processing device 1 may be used to perform the corresponding steps in the method provided by the embodiments of the present application. As shown in fig. 23, the system data processing apparatus 1 may include: the system comprises a service metadata acquisition module 11, a device instance establishment module 12, a sensor instance establishment module 13, a node configuration module 14 and a system modeling module 15;
wherein, the service metadata acquisition module 11 is configured to acquire service metadata for performing system modeling from a service data table associated with a service processing system; the service processing system comprises service equipment deployed in a physical space; the service equipment is provided with an equipment sensor;
the device instance establishing module 12 is configured to establish a device instance of the service device based on the device class metadata when the device class metadata of the service device exists in the service metadata; the equipment instance is used for recording equipment class nodes and equipment nodes of the service equipment; the device node is subordinate to the device class node;
A sensor instance establishing module 13, configured to establish a sensor instance of a device sensor deployed on a service device based on sensor class metadata when the sensor class metadata of the device sensor exists in the service metadata; the sensor instance is used for recording sensor class nodes and sensor nodes of the equipment sensor; the sensor node is subordinate to the sensor class node;
a node configuration module 14, configured to configure the device node in the device instance as a device master node and the sensor node in the sensor instance as a device child node subordinate to the device master node based on the device affiliation between the service device and the device sensor;
the system modeling module 15 is configured to obtain a system modeling model of the service processing system based on the equipment class node, the equipment main node, the sensor class node and the equipment sub-node by modeling; the system modeling model is used to query device dependencies between business devices and device sensors.
The service data table comprises N rows of table data; n is a positive integer greater than 1; among the N rows of table data, the ith row of table data is used for recording the equipment data information of the business equipment, and the jth row of table data is used for recording the sensor data information of the equipment sensor; i is not equal to j, and i and j are positive integers less than or equal to N;
The service metadata acquisition module 11 includes:
a service data table acquiring unit 111, configured to acquire a service data table associated with a service processing system;
a table data reading unit 112, configured to, in a service data table including N rows of table data, when the ith row of table data in the N rows of table data is read, obtain device data information of the service device recorded in the ith row of table data, and use the read device data information as device metadata of the service device in a modeling mapping space corresponding to a physical space; modeling map space is different from physical space;
the table data reading unit 112 is further configured to, in a service data table including N rows of table data, when reading the jth row of table data in the N rows of table data, obtain sensor data information of the device sensor recorded in the jth row of table data, and use the read sensor data information as sensor metadata of the device sensor in the modeling mapping space;
a service metadata determining unit 113 for determining the device metadata and the sensor metadata as service metadata for performing system modeling.
The service metadata at least comprises equipment metadata of the service equipment in a modeling mapping space corresponding to the physical space; the device metadata includes entity names, entity types, and entity namespaces of entity devices located in the modeling mapping space; the entity equipment is an entity of the service equipment in the modeling mapping space; modeling map space is different from physical space;
The device instance creation module 12 includes:
a first data traversing unit 121, configured to obtain device metadata from the service metadata in a traversing manner;
the first data traversing unit 121 is further configured to determine that, if the entity type of the entity device is determined to be the device type in the device metadata obtained by traversing, device type metadata of the service device exists in the service metadata;
the device instance creation unit 122 is configured to configure device attribute information for the entity device based on the device class metadata, and create a device instance of the service device based on the configured device attribute information, the entity name of the entity device, and the entity namespace of the entity device.
The device class metadata comprises entity names, entity types, entity namespaces and entity attribute types of entity devices mapped by the service devices; the entity equipment is an entity of the service equipment in a modeling mapping space corresponding to the physical space; modeling map space is different from physical space;
the device instance creation module 12 includes:
a first node configuration unit 123, configured to obtain an entity name of the entity device in the device class metadata when the entity type of the entity device is the device type, and determine a node configured for the entity name of the entity device as a device node of the service device in the modeling mapping space;
The first node configuration unit 123 is further configured to obtain an entity attribute type of the entity device in the device class metadata when the entity namespace of the entity device belongs to the first namespace, and determine a node configured for the entity attribute type of the entity device in the first namespace as a device class node of the service device in the modeling mapping space;
a first attribute configuration unit 124, configured to configure device attribute information for the entity device based on an attribute membership between an entity name of the entity device and an entity attribute type of the entity device;
and the device instance creation unit is used for constructing a node pointing relationship between the device node and the device class node based on the configured device attribute information, and generating a device instance of the service device based on the node pointing relationship between the device node and the device class node.
Wherein, the first node configuration unit 123 is further configured to:
and when the entity name space of the entity equipment belongs to the second name space, acquiring the entity attribute type of the entity equipment in the equipment type metadata, and determining the node configured for the entity attribute type of the entity equipment in the second name space as the equipment type node of the entity attribute type in the modeling mapping space.
Wherein the first node configuration unit 123 includes:
a first name obtaining subunit 1231, configured to obtain, when the entity type of the entity device is a device type, an entity name of the entity device in the device class metadata;
the first label configuration subunit 1232 is configured to add a device attribute label to a node configured for the entity name of the entity device based on the entity name of the entity device, and determine the node configured for the entity name of the entity device and added with the device attribute label as a device node of the service device in the modeling mapping space.
The service metadata at least comprises sensor metadata of the equipment sensor in a modeling mapping space corresponding to the physical space; the sensor metadata includes entity names, entity types, and entity namespaces of entity sensors located in the modeling mapping space; the entity sensor is an entity of the equipment sensor in the modeling mapping space; modeling map space is different from physical space;
the sensor instance creation module 13 includes:
a second data traversing unit 131, configured to obtain sensor metadata from the service metadata in a traversing manner;
the second data traversing unit 131 is further configured to determine that sensor metadata of the device sensor exists in the service metadata if it is determined that the entity type of the entity sensor is the sensor type in the sensor metadata acquired by traversing;
The sensor instance creation unit 132 is configured to configure sensor attribute information for the entity sensor based on the sensor class metadata, and create a sensor instance of the device sensor based on the configured sensor attribute information, the entity name of the entity sensor, and the entity namespace of the entity sensor.
The sensor class metadata comprises entity names, entity types, entity namespaces and entity attribute types of entity sensors mapped by the device sensors; the entity sensor is an entity in a modeling mapping space corresponding to the physical space of the equipment sensor; modeling map space is different from physical space;
the sensor instance creation module 13 includes:
a second node configuration unit 133, configured to obtain, when the entity type of the entity sensor is a sensor type, an entity name of the entity sensor in the sensor type metadata, and determine a node configured for the entity name of the entity sensor as a sensor node of the device sensor in the modeling mapping space;
the second node configuration unit 133 is further configured to obtain an entity attribute type of the entity sensor in the sensor class metadata when the entity namespace of the entity sensor belongs to the first namespace, and determine a node configured for the entity attribute type of the entity sensor in the first namespace as a sensor class node of the entity attribute type of the device sensor in the modeling mapping space;
A second attribute configuration unit 134, configured to configure sensor attribute information for the entity sensor based on an attribute membership between an entity name of the entity sensor and an entity attribute type of the entity sensor;
and the sensor instance creation unit is used for constructing a node pointing relation between the sensor nodes and the sensor class nodes based on the configured sensor attribute information, and generating a sensor instance of the device sensor based on the node pointing relation between the sensor nodes and the sensor class nodes.
Wherein the second node configuration unit 133 is further configured to:
and when the entity namespaces of the entity sensors belong to the second namespaces, acquiring entity attribute types of the entity sensors in the sensor class metadata, and determining nodes configured for the entity attribute types of the entity sensors in the second namespaces as sensor class nodes of the entity attribute types of the equipment sensors in the modeling mapping space.
Wherein the second node configuration unit 133 includes:
a second name obtaining subunit 1331, configured to obtain, when the entity type of the entity sensor is a sensor type, an entity name of the entity sensor in the sensor type metadata;
A second tag configuration subunit 1332, configured to add a sensor attribute tag to the node configured for the entity name of the entity sensor based on the entity name of the entity sensor, and determine the node configured for the entity name of the entity sensor and added with the sensor attribute tag as a sensor node of the device sensor in the modeling map space.
Wherein the sensor class metadata further comprises an entity attribute measurement unit of the entity sensor;
the sensor instance creation module 13 further includes:
an attribute node configuration unit 135 for determining a node configured for an entity attribute measurement unit of an entity sensor as a first sensor attribute node of a device sensor in a modeling map space;
the attribute node configuration unit 135 is further configured to construct a node pointing relationship between the sensor node and the first sensor attribute node based on an attribute subordinate relationship between the entity name of the entity sensor and the entity attribute measurement unit of the entity sensor;
an instance updating unit 136 for updating the sensor instance of the device sensor based on the node pointing relationship between the sensor node and the first sensor attribute node.
Wherein the sensor class metadata further comprises entity attribute measurement data of the entity sensor;
The sensor instance creation module 13 further includes:
an attribute node configuration unit 135 for determining a node configured for the physical attribute measurement data of the physical sensor as a second sensor attribute node of the device sensor in the modeling map space;
the attribute node configuration unit 135 is further configured to construct a node pointing relationship between the sensor node and the second sensor attribute node based on the attribute subordinate relationship between the entity name of the entity sensor and the entity attribute measurement data of the entity sensor;
an instance updating unit 136 for updating the sensor instance of the device sensor based on the node pointing relationship between the sensor node and the second sensor attribute node.
Wherein the entity attribute measurement data comprises: a measurement data storage identifier and a measurement data storage location;
the attribute node configuration unit 135 is further configured to:
the method comprises the steps that nodes configured for measuring data storage identification of an entity sensor are determined to be storage identification attribute nodes of a device sensor in a modeling mapping space;
determining a node configured for a measured data storage location of the entity sensor as a storage location attribute node of the device sensor in a modeling mapping space;
Generating a target storage attribute node associated with the storage identification attribute node and the storage location attribute node, determining a node configured for the entity attribute measurement data of the entity sensor based on the target storage attribute node; the target storage attribute node is subordinate to the storage identification attribute node and subordinate to the storage location attribute node.
The service equipment comprises first service equipment and second service equipment;
the system modeling module 15 further includes:
a device connection unit 151, configured to construct a device node pointing relationship between a device node in a device instance of the first service device and a device node in a device instance of the second service device based on a device connection relationship between the first service device and the second service device in a physical space;
the model updating unit 152 is configured to update a system modeling model of the service processing system based on the device node pointing relationship, so as to obtain an updated system modeling model; the updated system modeling model is used for inquiring the device connection relation between the first service device and the second service device.
The system modeling model comprises storage identification attribute nodes belonging to the equipment sub-nodes corresponding to the equipment sensors, wherein the storage identification attribute nodes are subordinate to the storage identification attribute nodes and subordinate to the storage position attribute nodes; the storage position attribute node is used for indicating a storage position corresponding to the operation measurement data of the equipment sensor, and the storage position attribute node is used for indicating a storage identifier of the operation measurement data of the equipment sensor in the storage position;
The system modeling module 15 further includes:
a request obtaining unit 153, configured to, when obtaining a data query request sent by a service object for a device sensor in a service processing system, query, based on a system modeling model, a storage identifier attribute node and a storage location attribute node associated with the device sensor, and obtain a storage identifier indicated by the storage identifier attribute node and obtain a storage location indicated by the storage location attribute node; the data query request is used for indicating a measurement data sequence matched with the query device sensor in the device operation period;
a data positioning unit 154 for positioning the operation measurement data of the device sensor based on the storage identifier and the storage location, and acquiring a measurement data sequence of the device sensor matched with the device operation period from the positioned operation measurement data of the device sensor; the sequence of measurement data is determined from operational measurement data obtained by the device sensor during the device operational period;
the data positioning unit 154 is further configured to return the measurement data sequence of the device sensor to the service terminal corresponding to the service object, so that the service terminal determines a system measurement data set of the service processing system based on the operation measurement data in the measurement data sequence.
Wherein the system modeling module 15 further comprises:
an anomaly detection unit 155 for acquiring anomaly detection conditions for anomaly detection of the system measurement data set, and performing data anomaly detection of the system measurement data set based on the anomaly detection conditions to obtain a data anomaly detection result;
the abnormality detection unit 155 is further configured to, if the data abnormality detection result indicates that the system measurement data set has operation measurement data satisfying the abnormality detection condition, take the operation measurement data satisfying the abnormality detection condition as the abnormality measurement data;
an anomaly detection unit 155 further configured to remove anomaly measurement data from the system measurement data set, and take the system measurement data set from which the anomaly measurement data has been removed as a target measurement data set;
the quality detection unit 156 is configured to perform data integrity detection on the target measurement data set based on the system measurement data set, obtain a data integrity detection result of the target measurement data set, determine data set quality information of the target measurement data set based on the data integrity detection result of the target measurement data set, and return the data set quality information to a service terminal corresponding to the service object.
The system measurement data set comprises a plurality of groups of operation measurement data obtained by the device sensor at a plurality of device operation moments in a device operation period; one device runtime corresponds to a set of operational measurement data;
The abnormality detection unit 155 includes:
an abnormal range obtaining subunit 1551, configured to obtain an abnormal range of measurement data corresponding to the operation measurement data, and determine an abnormal detection condition based on the abnormal range of measurement data;
the anomaly detection subunit 1552 is configured to determine that the reference operation measurement data satisfies the anomaly detection condition if it is determined that the reference operation measurement data in the plurality of sets of operation measurement data belongs to the measurement data anomaly range based on the anomaly detection condition, and obtain a data anomaly detection result based on the reference operation measurement data.
The specific implementation manners of the service metadata obtaining module 11, the device instance establishing module 12, the sensor instance establishing module 13, the node configuration module 14, and the system modeling module 15 may be referred to the related descriptions in the above embodiments, and will not be further described herein. It should be understood that the description of the beneficial effects obtained by the same method will not be repeated.
Further, referring to fig. 24, fig. 24 is a schematic structural diagram of a computer device according to an embodiment of the present application. As shown in fig. 24, the computer device 1900 may be a service terminal or a server, which is not limited herein. For ease of understanding, the present application takes a computer device as an example of a server, and the computer device 1900 may include: processor 1901, network interface 1904 and memory 1905, and in addition, the computer device 1900 may include: a user interface 1903, and at least one communication bus 1902. Wherein a communication bus 1902 is used to enable connected communications between these components. The user interface 1903 may also include a standard wired interface, a wireless interface, among others. The network interface 1904 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1905 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 1905 may also optionally be at least one storage device located remotely from the processor 1901. As shown in fig. 24, an operating system, a network communication module, a user interface module, and a device control application program may be included in the memory 1905 as one type of computer-readable storage medium.
Wherein the network interface 1904 in the computer device 1900 may also provide network data interaction functionality. In the computer device 1900 shown in FIG. 24, a network interface 1904 may provide network data interaction functions; while user interface 1903 is primarily an interface for providing input to a user; the processor 1901 may be configured to invoke the device control application stored in the memory 1905 to execute the description of the system data processing method in the embodiment corresponding to fig. 3 and fig. 9, and may also execute the description of the system data processing apparatus 1 in the embodiment corresponding to fig. 23, which is not described herein. In addition, the description of the beneficial effects of the same method is omitted.
In one possible implementation, the memory 1905 is used to store program instructions. The processor 1901 may invoke program instructions to perform the following steps:
acquiring service metadata for system modeling from a service data table associated with a service processing system; the service processing system comprises service equipment deployed in a physical space; the service equipment is provided with an equipment sensor;
when equipment type metadata of the service equipment exists in the service metadata, establishing an equipment instance of the service equipment based on the equipment type metadata; the equipment instance is used for recording equipment class nodes and equipment nodes of the service equipment; the device node is subordinate to the device class node;
When the sensor class metadata of the device sensors deployed on the service device exist in the service metadata, establishing a sensor instance of the device sensors based on the sensor class metadata; the sensor instance is used for recording sensor class nodes and sensor nodes of the equipment sensor; the sensor node is subordinate to the sensor class node;
based on the device subordinate relation between the service device and the device sensor, configuring the device node in the device instance as a device master node, and configuring the sensor node in the sensor instance as a device child node subordinate to the device master node;
based on the equipment class node, the equipment main node, the sensor class node and the equipment sub-node, modeling to obtain a system modeling model of the service processing system; the system modeling model is used to query device dependencies between business devices and device sensors.
The service data table comprises N rows of table data; n is a positive integer greater than 1; among the N rows of table data, the ith row of table data is used for recording the equipment data information of the business equipment, and the jth row of table data is used for recording the sensor data information of the equipment sensor; i is not equal to j, and i and j are positive integers less than or equal to N;
The processor 1901, when used to obtain business metadata for system modeling from a business data table associated with a business processing system, is specifically configured to:
acquiring a service data table associated with a service processing system;
in a service data table containing N rows of table data, when the ith row of table data in the N rows of table data is read, acquiring the equipment data information of the service equipment recorded in the ith row of table data, and taking the read equipment data information as the equipment metadata of the service equipment in a modeling mapping space corresponding to a physical space; modeling map space is different from physical space;
in a business data table containing N rows of table data, when the jth row of table data in the N rows of table data is read, acquiring sensor data information of the equipment sensor recorded in the jth row of table data, and taking the read sensor data information as sensor metadata of the equipment sensor in a modeling mapping space;
the device metadata and the sensor metadata are determined as business metadata for system modeling.
The service metadata at least comprises equipment metadata of the service equipment in a modeling mapping space corresponding to the physical space; the device metadata includes entity names, entity types, and entity namespaces of entity devices located in the modeling mapping space; the entity equipment is an entity of the service equipment in the modeling mapping space; modeling map space is different from physical space;
The processor 1901, when configured to establish a device instance of the service device based on the device class metadata when the device class metadata of the service device exists in the service metadata, is specifically configured to:
traversing and acquiring device metadata from the service metadata;
if the entity type of the entity equipment is determined to be the equipment type in the equipment metadata obtained by traversing, equipment type metadata of the service equipment is determined to exist in the service metadata;
and configuring equipment attribute information for the entity equipment based on the equipment type metadata, and establishing an equipment instance of the service equipment based on the configured equipment attribute information, the entity name of the entity equipment and the entity name space of the entity equipment.
The device class metadata comprises entity names, entity types, entity namespaces and entity attribute types of entity devices mapped by the service devices; the entity equipment is an entity of the service equipment in a modeling mapping space corresponding to the physical space; modeling map space is different from physical space;
the processor 1901, when configured to establish a device instance of the service device based on the device class metadata when the device class metadata of the service device exists in the service metadata, is specifically configured to:
When the entity type of the entity equipment is the equipment type, acquiring the entity name of the entity equipment in the equipment type metadata, and determining the node configured for the entity name of the entity equipment as the equipment node of the service equipment in the modeling mapping space;
when the entity name space of the entity equipment belongs to a first name space, acquiring the entity attribute type of the entity equipment in the equipment type metadata, and determining a node configured for the entity attribute type of the entity equipment in the first name space as an equipment type node of the service equipment in a modeling mapping space;
configuring equipment attribute information for the entity equipment based on the attribute subordinate relation between the entity name of the entity equipment and the entity attribute type of the entity equipment;
and constructing a node pointing relationship between the equipment nodes and the equipment class nodes based on the configured equipment attribute information, and generating an equipment instance of the service equipment based on the node pointing relationship between the equipment nodes and the equipment class nodes.
Wherein the processor 1901 is further configured to:
and when the entity name space of the entity equipment belongs to the second name space, acquiring the entity attribute type of the entity equipment in the equipment type metadata, and determining the node configured for the entity attribute type of the entity equipment in the second name space as the equipment type node of the entity attribute type in the modeling mapping space.
The processor 1901 is configured to obtain, when the entity type of the entity device is the device type, the entity name of the entity device in the device type metadata, and determine a node configured for the entity name as a device node of the service device in the modeling mapping space, where the method is specifically configured to:
when the entity type of the entity equipment is the equipment type, acquiring the entity name of the entity equipment in the equipment type metadata;
and adding a device attribute label to the node configured for the entity name of the entity device based on the entity name of the entity device, and determining the node configured for the entity name of the entity device and added with the device attribute label as the device node of the service device in the modeling mapping space.
The service metadata at least comprises sensor metadata of the equipment sensor in a modeling mapping space corresponding to the physical space; the sensor metadata includes entity names, entity types, and entity namespaces of entity sensors located in the modeling mapping space; the entity sensor is an entity of the equipment sensor in the modeling mapping space; modeling map space is different from physical space;
the processor 1901, when used for creating a sensor instance of a device sensor deployed on a business device based on sensor class metadata when there is sensor class metadata for the device sensor in the business metadata, is specifically configured to:
Traversing and acquiring sensor metadata from service metadata;
if the entity type of the entity sensor is determined to be the sensor type in the sensor metadata obtained by traversing, determining that the sensor type metadata of the equipment sensor exists in the service metadata;
configuring sensor attribute information for the entity sensor based on the sensor class metadata, and establishing a sensor instance of the device sensor based on the configured sensor attribute information, the entity name of the entity sensor and the entity namespace of the entity sensor.
The sensor class metadata comprises entity names, entity types, entity namespaces and entity attribute types of entity sensors mapped by the device sensors; the entity sensor is an entity in a modeling mapping space corresponding to the physical space of the equipment sensor; modeling map space is different from physical space;
the processor 1901, when used for creating a sensor instance of a device sensor deployed on a business device based on sensor class metadata when there is sensor class metadata for the device sensor in the business metadata, is specifically configured to:
when the entity type of the entity sensor is the sensor type, acquiring the entity name of the entity sensor in the sensor type metadata, and determining the node configured for the entity name of the entity sensor as a sensor node of the equipment sensor in the modeling mapping space;
When the entity name space of the entity sensor belongs to a first name space, acquiring the entity attribute type of the entity sensor in the sensor class metadata, and determining a node configured for the entity attribute type of the entity sensor in the first name space as a sensor class node of the entity attribute type of the equipment sensor in a modeling mapping space;
configuring sensor attribute information for the entity sensor based on an attribute subordinate relation between the entity name of the entity sensor and the entity attribute type of the entity sensor;
and constructing a node pointing relationship between the sensor nodes and the sensor class nodes based on the configured sensor attribute information, and generating a sensor instance of the device sensor based on the node pointing relationship between the sensor nodes and the sensor class nodes.
Wherein the processor 1901 is further configured to:
and when the entity namespaces of the entity sensors belong to the second namespaces, acquiring entity attribute types of the entity sensors in the sensor class metadata, and determining nodes configured for the entity attribute types of the entity sensors in the second namespaces as sensor class nodes of the entity attribute types of the equipment sensors in the modeling mapping space.
The processor 1901 is configured to obtain, when the entity type of the entity sensor is a sensor type, an entity name of the entity sensor in the sensor type metadata, and determine a node configured for the entity name of the entity sensor as a sensor node of the device sensor in the modeling mapping space, where the node is specifically configured to:
when the entity type of the entity sensor is the sensor type, acquiring the entity name of the entity sensor in the sensor type metadata;
and adding a sensor attribute label to the nodes configured for the entity names of the entity sensors based on the entity names of the entity sensors, and determining the nodes configured for the entity names of the entity sensors and added with the sensor attribute label as sensor nodes of the device sensors in the modeling mapping space.
Wherein the sensor class metadata further comprises an entity attribute measurement unit of the entity sensor;
the processor 1901 is also configured to:
determining a node configured for an entity attribute measurement unit of an entity sensor as a first sensor attribute node of a device sensor in a modeling mapping space;
constructing a node pointing relationship between a sensor node and a first sensor attribute node based on an attribute subordinate relationship between an entity name of an entity sensor and an entity attribute measurement unit of the entity sensor;
The sensor instance of the device sensor is updated based on the node pointing relationship between the sensor node and the first sensor attribute node.
Wherein the sensor class metadata further comprises entity attribute measurement data of the entity sensor;
the processor 1901 is also configured to:
determining a node configured for the physical attribute measurement data of the physical sensor as a second sensor attribute node of the device sensor in the modeling mapping space;
constructing a node pointing relationship between a sensor node and a second sensor attribute node based on the attribute subordinate relationship between the entity name of the entity sensor and the entity attribute measurement data of the entity sensor;
the sensor instance of the device sensor is updated based on the node pointing relationship between the sensor node and the second sensor attribute node.
Wherein the entity attribute measurement data comprises: a measurement data storage identifier and a measurement data storage location;
the processor 1901 is also configured to:
the method comprises the steps that nodes configured for measuring data storage identification of an entity sensor are determined to be storage identification attribute nodes of a device sensor in a modeling mapping space;
determining a node configured for a measured data storage location of the entity sensor as a storage location attribute node of the device sensor in a modeling mapping space;
Generating a target storage attribute node associated with the storage identification attribute node and the storage location attribute node, determining a node configured for the entity attribute measurement data of the entity sensor based on the target storage attribute node; the target storage attribute node is subordinate to the storage identification attribute node and subordinate to the storage location attribute node.
The service equipment comprises first service equipment and second service equipment;
the processor 1901 is also configured to:
constructing a device node pointing relationship between a device node in a device instance of the first service device and a device node in a device instance of the second service device based on the device connection relationship between the first service device and the second service device in the physical space;
updating a system modeling model of the service processing system based on the equipment node pointing relation to obtain an updated system modeling model; the updated system modeling model is used for inquiring the device connection relation between the first service device and the second service device.
The system modeling model comprises storage identification attribute nodes belonging to the equipment sub-nodes corresponding to the equipment sensors, wherein the storage identification attribute nodes are subordinate to the storage identification attribute nodes and subordinate to the storage position attribute nodes; the storage position attribute node is used for indicating a storage position corresponding to the operation measurement data of the equipment sensor, and the storage position attribute node is used for indicating a storage identifier of the operation measurement data of the equipment sensor in the storage position;
The processor 1901 is also configured to:
when a data query request sent by a business object aiming at a device sensor in a business processing system is obtained, a storage identification attribute node and a storage position attribute node associated with the device sensor are obtained based on a system modeling model query, and a storage identification indicated by the storage identification attribute node and a storage position indicated by the storage position attribute node are obtained; the data query request is used for indicating a measurement data sequence matched with the query device sensor in the device operation period;
positioning operation measurement data of the equipment sensor based on the storage identifier and the storage position, and acquiring a measurement data sequence matched with the equipment operation time period of the equipment sensor from the positioned operation measurement data of the equipment sensor; the sequence of measurement data is determined from operational measurement data obtained by the device sensor during the device operational period;
and returning the measurement data sequence of the equipment sensor to the service terminal corresponding to the service object so that the service terminal determines a system measurement data set of the service processing system based on the operation measurement data in the measurement data sequence.
Wherein the processor 1901 is further configured to:
Acquiring an abnormality detection condition for carrying out abnormality detection on the system measurement data set, and carrying out data abnormality detection on the system measurement data set based on the abnormality detection condition to obtain a data abnormality detection result;
if the data abnormality detection result indicates that the system measurement data set has operation measurement data meeting the abnormality detection condition, the operation measurement data meeting the abnormality detection condition is used as the abnormality measurement data;
removing the abnormal measurement data from the system measurement data set, and taking the system measurement data set after the abnormal measurement data is removed as a target measurement data set;
and carrying out data integrity detection on the target measurement data set based on the system measurement data set to obtain a data integrity detection result of the target measurement data set, determining data set quality information of the target measurement data set based on the data integrity detection result of the target measurement data set, and returning the data set quality information to a service terminal corresponding to the service object.
The system measurement data set comprises a plurality of groups of operation measurement data obtained by the device sensor at a plurality of device operation moments in a device operation period; one device runtime corresponds to a set of operational measurement data;
The processor 1901 is configured to, when acquiring an abnormality detection condition for detecting an abnormality of the system measurement data set, perform data abnormality detection on the system measurement data set based on the abnormality detection condition to obtain a data abnormality detection result, specifically:
acquiring a measurement data abnormal range corresponding to the operation measurement data, and determining an abnormal detection condition based on the measurement data abnormal range;
if the reference operation measurement data in the plurality of groups of operation measurement data belongs to the measurement data abnormal range based on the abnormal detection conditions, the reference operation measurement data is determined to meet the abnormal detection conditions, and a data abnormal detection result is obtained based on the reference operation measurement data.
In a specific implementation, the apparatus, the processor 1901, the memory 1905, and the like described in the embodiments of the present application may perform the implementation described in the above method embodiments, and may also perform the implementation described in the embodiments of the present application, which is not described herein again.
Furthermore, it should be noted here that: the embodiment of the present application further provides a computer readable storage medium, in which a computer program executed by the system data processing apparatus 1 mentioned above is stored, and the computer program includes computer instructions, when executed by a processor, can execute the description of the system data processing method in the embodiment corresponding to fig. 3 and fig. 9, and therefore, a description will not be repeated here. In addition, the description of the beneficial effects of the same method is omitted. For technical details not disclosed in the embodiments of the computer-readable storage medium according to the present application, please refer to the description of the method embodiments of the present application. As an example, computer instructions may be deployed to be executed on one computing device or on multiple computing devices at one site or, alternatively, across multiple computing devices distributed across multiple sites and interconnected by a communication network, where the multiple computing devices distributed across multiple sites and interconnected by a communication network may constitute a blockchain system.
In addition, it should be noted that: embodiments of the present application also provide a computer program product or computer program that may include computer instructions that may be stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor may execute the computer instructions, so that the computer device performs the description of the system data processing method in the embodiment corresponding to fig. 3 and fig. 9, and therefore, a detailed description will not be given here. In addition, the description of the beneficial effects of the same method is omitted. For technical details not disclosed in the computer program product or the computer program embodiments according to the present application, reference is made to the description of the method embodiments according to the present application.
It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of action combinations, but it should be understood by those skilled in the art that the present application is not limited by the order of action described, as some steps may be performed in other order or simultaneously according to the present application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily required for the present application.
The steps in the method of the embodiment of the application can be sequentially adjusted, combined and deleted according to actual needs.
The modules in the device of the embodiment of the application can be combined, divided and deleted according to actual needs.
Those skilled in the art will appreciate that implementing all or part of the above-described methods may be accomplished by way of a computer program stored in a computer-readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), or the like.
The foregoing disclosure is illustrative of the present application and is not to be construed as limiting the scope of the application, which is defined by the appended claims.
Claims (20)
1. A system data processing method, the method comprising:
acquiring service metadata for system modeling from a service data table associated with a service processing system; the service processing system comprises service equipment deployed in a physical space; the service equipment is provided with an equipment sensor;
When the equipment type metadata of the service equipment exist in the service metadata, establishing an equipment instance of the service equipment based on the equipment type metadata; the equipment instance is used for recording equipment class nodes and equipment nodes of the service equipment; the device node is subordinate to the device class node;
when the sensor class metadata of the device sensor deployed on the service device exists in the service metadata, establishing a sensor instance of the device sensor based on the sensor class metadata; the sensor instance is used for recording sensor class nodes and sensor nodes of the device sensor; the sensor node is subordinate to the sensor class node;
based on the device subordinate relation between the service device and the device sensor, configuring a device node in the device instance as a device master node, and configuring the sensor node in the sensor instance as a device child node subordinate to the device master node;
based on the equipment class node, the equipment main node, the sensor class node and the equipment sub node, modeling to obtain a system modeling model of the service processing system; the system modeling model is used for querying the device affiliation between the business device and the device sensor.
2. The method of claim 1, wherein the service data table comprises N rows of table data; n is a positive integer greater than 1; among the N rows of table data, the ith row of table data is used for recording the equipment data information of the business equipment, and the jth row of table data is used for recording the sensor data information of the equipment sensor; i is not equal to j, and i and j are positive integers less than or equal to N;
the obtaining service metadata for system modeling from a service data table associated with a service processing system comprises:
acquiring the service data table associated with the service processing system;
in the service data table containing the N rows of table data, when the ith row of table data in the N rows of table data is read, acquiring the equipment data information of the service equipment recorded in the ith row of table data, and taking the read equipment data information as the equipment metadata of the service equipment in the modeling mapping space corresponding to the physical space; the modeling mapping space is different from the physical space;
in the business data table containing the N rows of table data, when the j row of table data in the N rows of table data is read, acquiring sensor data information of the equipment sensor recorded in the j row of table data, and taking the read sensor data information as sensor metadata of the equipment sensor in the modeling mapping space;
And determining the device metadata and the sensor metadata as business metadata for system modeling.
3. The method according to claim 1, wherein the service metadata at least includes device metadata of the service device in a modeling mapping space corresponding to the physical space; the device metadata includes entity names, entity types, and entity namespaces of entity devices located in the modeling mapping space; the entity equipment is an entity of the service equipment in the modeling mapping space; the modeling mapping space is different from the physical space;
when the equipment type metadata of the service equipment exists in the service metadata, establishing an equipment instance of the service equipment based on the equipment type metadata, wherein the equipment instance comprises the following steps:
traversing and acquiring the equipment metadata from the service metadata;
if the entity type of the entity equipment is determined to be the equipment type in the equipment metadata obtained by traversing, determining that equipment type metadata of the service equipment exists in the service metadata;
and configuring equipment attribute information for the entity equipment based on the equipment type metadata, and establishing an equipment instance of the service equipment based on the configured equipment attribute information, the entity name of the entity equipment and the entity name space of the entity equipment.
4. The method of claim 1, wherein the device class metadata includes entity names, entity types, entity namespaces, and entity attribute types of entity devices to which the business devices map; the entity equipment is an entity of the service equipment in a modeling mapping space corresponding to the physical space; the modeling mapping space is different from the physical space;
when the equipment type metadata of the service equipment exists in the service metadata, establishing an equipment instance of the service equipment based on the equipment type metadata, wherein the equipment instance comprises the following steps:
when the entity type of the entity equipment is the equipment type, acquiring the entity name of the entity equipment in the equipment type metadata, and determining the node configured for the entity name of the entity equipment as the equipment node of the service equipment in the modeling mapping space;
when the entity name space of the entity equipment belongs to a first name space, acquiring the entity attribute type of the entity equipment in the equipment type metadata, and determining a node configured for the entity attribute type of the entity equipment in the first name space as an equipment type node of the service equipment in the modeling mapping space;
Configuring equipment attribute information for the entity equipment based on an attribute subordinate relation between the entity name of the entity equipment and the entity attribute type of the entity equipment;
and constructing a node pointing relationship between the equipment node and the equipment class node based on the configured equipment attribute information, and generating an equipment instance of the service equipment based on the node pointing relationship between the equipment node and the equipment class node.
5. The method according to claim 4, wherein the method further comprises:
and when the entity name space of the entity equipment belongs to a second name space, acquiring the entity attribute type of the entity equipment in the equipment type metadata, and determining the node configured for the entity attribute type of the entity equipment in the second name space as the equipment type node of the entity attribute type in the modeling mapping space.
6. The method according to claim 4, wherein when the entity type of the entity device is a device type, acquiring the entity name of the entity device in the device type metadata, and determining the node configured for the entity name as the device node of the service device in the modeling mapping space includes:
When the entity type of the entity equipment is the equipment type, acquiring the entity name of the entity equipment in the equipment type metadata;
and adding a device attribute label to the node configured for the entity name of the entity device based on the entity name of the entity device, and determining the node configured for the entity name of the entity device and added with the device attribute label as the device node of the service device in the modeling mapping space.
7. The method according to claim 1, wherein the service metadata at least comprises sensor metadata of the device sensor in a modeling mapping space corresponding to the physical space; the sensor metadata includes entity names, entity types, and entity namespaces of entity sensors located in the modeling mapping space; the entity sensor is an entity of the device sensor in the modeling mapping space; the modeling mapping space is different from the physical space;
when the sensor class metadata of the device sensor deployed on the service device exists in the service metadata, establishing a sensor instance of the device sensor based on the sensor class metadata, including:
Traversing and acquiring the sensor metadata from the service metadata;
if the entity type of the entity sensor is determined to be the sensor type in the sensor metadata obtained by traversing, determining that the sensor type metadata of the equipment sensor exists in the service metadata;
configuring sensor attribute information for the entity sensor based on the sensor class metadata, and establishing a sensor instance of the device sensor based on the configured sensor attribute information, the entity name of the entity sensor and the entity namespace of the entity sensor.
8. The method of claim 1, wherein the sensor class metadata includes entity names, entity types, entity namespaces, and entity attribute types of entity sensors to which the device sensors map; the entity sensor is an entity of the equipment sensor in a modeling mapping space corresponding to the physical space; the modeling mapping space is different from the physical space;
when the sensor class metadata of the device sensor deployed on the service device exists in the service metadata, establishing a sensor instance of the device sensor based on the sensor class metadata, including:
When the entity type of the entity sensor is a sensor type, acquiring the entity name of the entity sensor in the sensor type metadata, and determining a node configured for the entity name of the entity sensor as a sensor node of the equipment sensor in the modeling mapping space;
when the entity namespace of the entity sensor belongs to a first namespace, acquiring the entity attribute type of the entity sensor in the sensor class metadata, and determining a node configured for the entity attribute type of the entity sensor in the first namespace as a sensor class node of the entity attribute type of the equipment sensor in the modeling mapping space;
configuring sensor attribute information for the entity sensor based on an attribute subordinate relationship between an entity name of the entity sensor and an entity attribute type of the entity sensor;
and constructing a node pointing relationship between the sensor nodes and the sensor class nodes based on the configured sensor attribute information, and generating a sensor instance of the equipment sensor based on the node pointing relationship between the sensor nodes and the sensor class nodes.
9. The method of claim 8, wherein the method further comprises:
and when the entity namespace of the entity sensor belongs to a second namespace, acquiring the entity attribute type of the entity sensor in the sensor class metadata, and determining the node configured for the entity attribute type of the entity sensor in the second namespace as the sensor class node of the entity attribute type of the equipment sensor in the modeling mapping space.
10. The method according to claim 8, wherein when the entity type of the entity sensor is a sensor type, acquiring the entity name of the entity sensor in the sensor class metadata, determining the node configured for the entity name of the entity sensor as the sensor node of the device sensor in the modeling mapping space, includes:
when the entity type of the entity sensor is a sensor type, acquiring the entity name of the entity sensor in the sensor type metadata;
and adding a sensor attribute label to the node configured for the entity name of the entity sensor based on the entity name of the entity sensor, and determining the node configured for the entity name of the entity sensor and added with the sensor attribute label as a sensor node of the equipment sensor in the modeling mapping space.
11. The method of claim 8, wherein the sensor class metadata further comprises entity attribute measurement units of the entity sensor;
the method further comprises the steps of:
determining a node configured for an entity attribute measurement unit of the entity sensor as a first sensor attribute node of the device sensor in the modeling mapping space;
constructing a node pointing relationship between the sensor node and the first sensor attribute node based on an attribute subordinate relationship between the entity name of the entity sensor and the entity attribute measurement unit of the entity sensor;
and updating the sensor instance of the device sensor based on the node pointing relationship between the sensor node and the first sensor attribute node.
12. The method of claim 8, wherein the sensor class metadata further comprises entity attribute measurement data for the entity sensor;
the method further comprises the steps of:
determining a node configured for the physical attribute measurement data of the physical sensor as a second sensor attribute node of the device sensor in the modeling mapping space;
Constructing a node pointing relationship between the sensor node and the second sensor attribute node based on the attribute subordinate relationship between the entity name of the entity sensor and the entity attribute measurement data of the entity sensor;
and updating the sensor instance of the device sensor based on the node pointing relationship between the sensor node and the second sensor attribute node.
13. The method of claim 12, wherein the entity attribute measurement data comprises: a measurement data storage identifier and a measurement data storage location;
the method further comprises the steps of:
determining a configured node for the measurement data storage identification of the physical sensor as a storage identification attribute node of the device sensor in the modeling mapping space;
determining a node configured for the measured data storage location of the physical sensor as a storage location attribute node of the device sensor in the modeling mapping space;
generating a target storage attribute node associated with the storage identification attribute node and the storage location attribute node, determining a node configured for entity attribute measurement data of the entity sensor based on the target storage attribute node; the target storage attribute node is subordinate to the storage identification attribute node and subordinate to the storage location attribute node.
14. The method of claim 1, wherein the service device comprises a first service device and a second service device;
the method further comprises the steps of:
constructing a device node pointing relationship between a device node in a device instance of the first service device and a device node in a device instance of the second service device based on the device connection relationship between the first service device and the second service device in the physical space;
updating a system modeling model of the service processing system based on the equipment node pointing relation to obtain an updated system modeling model; the updated system modeling model is used for inquiring the equipment connection relation between the first service equipment and the second service equipment.
15. The method of claim 1, wherein the system modeling model includes a storage identification attribute node subordinate to the device sub-node to which the device sensor corresponds, the storage identification attribute node subordinate to the storage identification attribute node and subordinate to the storage location attribute node; the storage position attribute node is used for indicating a storage position corresponding to the operation measurement data of the equipment sensor, and the storage position attribute node is used for indicating a storage identifier of the operation measurement data of the equipment sensor in the storage position;
The method further comprises the steps of:
when a data query request of a business object sent by aiming at the equipment sensor in the business processing system is obtained, inquiring the storage identification attribute node and the storage position attribute node associated with the equipment sensor based on the system modeling model, and obtaining a storage identification indicated by the storage identification attribute node and a storage position indicated by the storage position attribute node; the data query request is used for indicating and querying a measurement data sequence matched by the equipment sensor in the equipment operation period;
positioning operation measurement data of the equipment sensor based on the storage identifier and the storage position, and acquiring a measurement data sequence matched with the equipment operation period of the equipment sensor from the positioned operation measurement data of the equipment sensor; the sequence of measurement data is determined from operational measurement data obtained by the device sensor over the device operational period;
and returning the measurement data sequence of the equipment sensor to a service terminal corresponding to the service object, so that the service terminal determines a system measurement data set of the service processing system based on the operation measurement data in the measurement data sequence.
16. The method of claim 15, wherein the method further comprises:
acquiring an abnormality detection condition for carrying out abnormality detection on the system measurement data set, and carrying out data abnormality detection on the system measurement data set based on the abnormality detection condition to obtain a data abnormality detection result;
if the data abnormality detection result indicates that the system measurement data set has operation measurement data meeting the abnormality detection condition, taking the operation measurement data meeting the abnormality detection condition as abnormality measurement data;
removing the abnormal measurement data from the system measurement data set, and taking the system measurement data set from which the abnormal measurement data is removed as a target measurement data set;
and carrying out data integrity detection on the target measurement data set based on the system measurement data set to obtain a data integrity detection result of the target measurement data set, determining data set quality information of the target measurement data set based on the data integrity detection result of the target measurement data set, and returning the data set quality information to a service terminal corresponding to the service object.
17. The method of claim 16, wherein the system measurement dataset comprises a plurality of sets of operational measurement data obtained by the device sensor at a plurality of device operational moments within the device operational period; one device runtime corresponds to a set of operational measurement data;
the obtaining an abnormality detection condition for performing abnormality detection on the system measurement data set, performing data abnormality detection on the system measurement data set based on the abnormality detection condition, to obtain a data abnormality detection result, including:
acquiring a measurement data abnormal range corresponding to the operation measurement data, and determining the abnormal detection condition based on the measurement data abnormal range;
and if the reference operation measurement data in the plurality of groups of operation measurement data belong to the measurement data abnormal range based on the abnormal detection condition, determining that the reference operation measurement data meet the abnormal detection condition, and obtaining the data abnormal detection result based on the reference operation measurement data.
18. A system data processing apparatus, the apparatus comprising:
the business metadata acquisition module is used for acquiring business metadata for system modeling from a business data table associated with the business processing system; the service processing system comprises service equipment deployed in a physical space; the service equipment is provided with an equipment sensor;
The device instance establishing module is used for establishing a device instance of the service device based on the device class metadata when the device class metadata of the service device exists in the service metadata; the equipment instance is used for recording equipment class nodes and equipment nodes of the service equipment; the device node is subordinate to the device class node;
a sensor instance establishing module, configured to establish a sensor instance of the device sensor based on sensor class metadata when there is sensor class metadata of the device sensor deployed on the service device in the service metadata; the sensor instance is used for recording sensor class nodes and sensor nodes of the device sensor; the sensor node is subordinate to the sensor class node;
a node configuration module, configured to configure an equipment node in the equipment instance as an equipment master node and configure the sensor node in the sensor instance as an equipment child node subordinate to the equipment master node based on an equipment subordinate relationship between the service equipment and the equipment sensor;
the system modeling module is used for modeling based on the equipment class node, the equipment main node, the sensor class node and the equipment sub node to obtain a system modeling model of the service processing system; the system modeling model is used for querying the device affiliation between the business device and the device sensor.
19. A computer device comprising a memory and a processor;
the memory is connected to the processor, the memory is used for storing a computer program, and the processor is used for calling the computer program to enable the computer device to execute the method of any one of claims 1-17.
20. A computer readable storage medium, characterized in that the computer readable storage medium has stored therein a computer program adapted to be loaded and executed by a processor to cause a computer device having the processor to perform the method of any of claims 1-17.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310757732.4A CN116976086A (en) | 2023-06-25 | 2023-06-25 | System data processing method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310757732.4A CN116976086A (en) | 2023-06-25 | 2023-06-25 | System data processing method, device, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116976086A true CN116976086A (en) | 2023-10-31 |
Family
ID=88472104
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310757732.4A Pending CN116976086A (en) | 2023-06-25 | 2023-06-25 | System data processing method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116976086A (en) |
-
2023
- 2023-06-25 CN CN202310757732.4A patent/CN116976086A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11238055B2 (en) | Building management system with eventseries processing | |
| US20240085877A1 (en) | Building management system with integration of data into smart entities | |
| Akbar et al. | Real-time probabilistic data fusion for large-scale IoT applications | |
| Fierro et al. | Shepherding metadata through the building lifecycle | |
| US10262262B2 (en) | Semantic method for terminal devices of internet of things | |
| Zhang et al. | Building information modeling–based cyber-physical platform for building performance monitoring | |
| WO2022083436A1 (en) | Data processing method and apparatus, and device and readable storage medium | |
| CN115115796A (en) | Building digital twin frame based on semantic Web technology and modeling method | |
| Ochian et al. | Big data search for environmental telemetry | |
| Nemirovski et al. | Ontological representation of knowledge related to building energy-efficiency | |
| US11836637B2 (en) | Construction method of human-object-space interaction model based on knowledge graph | |
| Xiao et al. | Building information modeling and building automation systems data integration and big data analytics for building energy management | |
| CN116976086A (en) | System data processing method, device, equipment and medium | |
| Ma et al. | An ontology-driven method for urban building energy modeling | |
| Song et al. | Research on enterprise cooperation management strategy analysis system based on knowledge transfer model | |
| Wang | [Retracted] Design of an Integrated System of Psychological Health Education Resources for Vocational Students Using Fuzzy Clustering Algorithm Analysis | |
| Guo et al. | Multisource target data fusion tracking method for heterogeneous network based on data mining | |
| Jin et al. | Research on multi-source heterogeneous sensor information fusion method under internet of things technology | |
| Li | Multidimensional Information Network Big Data Mining Algorithm Relying on Finite Element Analysis | |
| Trung | Database performance evaluation and applications of data science for IoT platform analysis | |
| Liu | Intelligent Community Management System Based on Big Data Technology | |
| Duarte Roa et al. | Towards a Stronger Foundation: Digitizing Commercial Buildings with Brick to Enable Portable Advanced Applications | |
| Li et al. | [Retracted] An Algorithm of Scene Information Collection in General Football Matches Based on Web Documents | |
| Ríos et al. | A big data test-bed for analyzing data generated by an air pollution sensor network | |
| Poletti et al. | A Real Data Analysis in an Internet of Things Environment. |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication |