CN116774645A - Method, device, medium and equipment for associating equipment object model with entity equipment - Google Patents
Method, device, medium and equipment for associating equipment object model with entity equipment Download PDFInfo
- Publication number
- CN116774645A CN116774645A CN202311059586.4A CN202311059586A CN116774645A CN 116774645 A CN116774645 A CN 116774645A CN 202311059586 A CN202311059586 A CN 202311059586A CN 116774645 A CN116774645 A CN 116774645A
- Authority
- CN
- China
- Prior art keywords
- equipment
- entity
- object model
- information
- plc
- 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
- 238000000034 method Methods 0.000 title claims abstract description 65
- 230000002159 abnormal effect Effects 0.000 claims abstract description 27
- 230000006870 function Effects 0.000 claims description 8
- 238000012795 verification Methods 0.000 claims description 4
- 238000004590 computer program Methods 0.000 claims description 3
- 238000010276 construction Methods 0.000 claims description 3
- 239000003245 coal Substances 0.000 description 16
- 238000010586 diagram Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 7
- 238000005065 mining Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 230000007613 environmental effect Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 238000004886 process control Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000000638 solvent extraction Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 238000012806 monitoring device Methods 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
- G05B19/05—Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
- G05B19/054—Input/output
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/10—Plc systems
- G05B2219/12—Plc mp multi processor system
- G05B2219/1207—Download programcode to node, I-O and execute programcode
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Automation & Control Theory (AREA)
- Software Systems (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mathematical Physics (AREA)
- Computational Linguistics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The disclosure relates to a method, a device, a medium and equipment for associating an equipment object model with entity equipment. The method comprises the following steps: constructing a database according to a process parameter library, an abnormal code dictionary and a PLC point table of the entity equipment; the technical parameters in the technical parameter library are defined technical parameters when the entity equipment leaves the factory, and the PLC point table at least comprises a PLC name, an address, acquisition frequency, a PLC substation and a unit; establishing an equipment object model according to the database; wherein, equipment thing model includes at least: device structure division, device attributes, abnormal code types and report account templates; acquiring entity equipment information, and importing equipment ledgers to obtain the entity equipment information with the equipment ledgers; and matching the entity equipment information with the equipment ledger with the equipment object model, and establishing a connection between the equipment object model and the entity equipment. The present disclosure may enable association between a device object model and an entity device.
Description
Technical Field
The disclosure relates to the technical field of communication, and in particular relates to a method, a device, a medium and equipment for associating an equipment object model with entity equipment.
Background
With the continuous development of the internet of things technology, more and more devices can be accessed into a network to form a huge device network, wherein the devices comprise automation devices, sensors, actuators, controllers and the like, and can be remotely monitored, controlled and managed through the internet. In order to realize effective management of these devices, it is necessary to build a standardized device object model to describe information such as properties and functions of the devices, and realize management of the devices through connection between the device object model and the entity devices. The interconnection and intercommunication among the hardware devices are realized in the mode, a technical basis is provided for collaborative integration work among the hardware devices, and the running reliability and stability among the devices are improved.
The equipment object model is a digital representation of an entity (such as a sensor, a vehicle-mounted device, a building, a factory and the like) in a physical space at the cloud, and comprises three dimensions of attributes, services and events, which describe what the entity can do and which information can be provided to the outside respectively. The connection manner between the equipment object model and the entity equipment in the related art still has some problems, and the main concentrated manifestations are as follows: 1. the standardized model of the equipment is not standard, the instantiation data reference is absent, and the reliability and completeness of the data are low; 2. the matching degree between the equipment object model and the entity equipment is not high when the equipment object model is used, the multiplexing rate is low, and the problem of insufficient resource utilization rate is caused; 3. the connection flow between the equipment object model and the entity equipment is complex and lacks unified specification, so that the acquired attribute cannot reach the pre-effect, and the problem of low utilization rate is caused.
Accordingly, there is a need to provide a new solution to ameliorate one or more of the problems presented in the above solutions.
It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
It is an object of the present disclosure to provide a method, apparatus, medium and device for associating an equipment object model with an entity device, thereby overcoming, at least in part, one or more of the problems due to the limitations and disadvantages of the related art.
According to a first aspect of an embodiment of the present disclosure, there is provided a method for associating an equipment object model with an entity device, including:
constructing a database according to a process parameter library, an abnormal code dictionary and a PLC point table of the entity equipment; the technical parameters in the technical parameter library are defined technical parameters when the entity equipment leaves the factory, and the PLC point table at least comprises a PLC name, an address, acquisition frequency, a PLC substation and a unit;
establishing an equipment object model according to the database; wherein, the equipment object model at least comprises: device structure division, device attributes, abnormal code types and report account templates;
acquiring entity equipment information, and importing an equipment ledger to obtain the entity equipment information with the equipment ledger; the entity equipment information at least comprises equipment type, equipment name, a using unit and a using place;
and matching the entity equipment information with the equipment ledger with the equipment object model, and establishing a connection between the equipment object model and the entity equipment.
In an embodiment of the disclosure, the step of establishing an equipment object model according to the database includes:
extracting entity equipment data information from the database according to the function and the characteristic of the mutual connection of the entity equipment;
establishing the equipment object model based on the entity equipment data information; the entity equipment data information at least comprises process parameter data, abnormal code data and PLC point table data.
In an embodiment of the disclosure, the step of matching the entity equipment information with the equipment ledger with the equipment object model includes:
binding the equipment object model with the entity equipment information with the equipment ledger according to a preset binding relation;
and verifying the preset binding relationship.
In the embodiment of the disclosure, the preset binding relationship is a relationship corresponding to the entity device information determined by matching a device identifier or the device type from the database.
In an embodiment of the disclosure, the step of establishing a connection between the equipment object model and the entity equipment includes:
and updating the equipment object model according to the state information of the actual existence of the entity equipment.
In an embodiment of the present disclosure, the step of updating the equipment object model according to the state information of the actual existence of the entity equipment includes:
and acquiring the state information of the entity equipment through the equipment object model, and sending the state information to a management center so that the management center generates updated information of the equipment object model.
In an embodiment of the present disclosure, the device attributes include a basic attribute, a service attribute, and an event attribute; the basic attributes are used for describing the running state of the equipment, and comprise equipment object model names, equipment object model types and equipment object model states; the service attribute is used for describing the capability or method of the equipment which can be called by the outside, and comprises a service which can be provided by the outside and is sent by a data acquisition and control instruction; the event attributes include notification information that needs to be externally sensed and processed, including messages of equipment failure or warning.
According to a second aspect of the embodiments of the present disclosure, there is provided an apparatus for associating an equipment object model with an entity device, including:
the construction module is used for constructing a database according to the process parameter library, the abnormal code dictionary and the PLC point table of the entity equipment; the technical parameters in the technical parameter library are defined technical parameters when the entity equipment leaves the factory, and the PLC point table at least comprises a PLC name, an address, acquisition frequency, a PLC substation and a unit;
the model building module is used for building an equipment object model according to the database; wherein, the equipment object model at least comprises: device structure division, device attributes, abnormal code types and report account templates;
the device comprises an acquisition module, a verification module and a verification module, wherein the acquisition module is used for acquiring entity equipment information and importing equipment ledgers to obtain the entity equipment information with the equipment ledgers; the entity equipment information at least comprises equipment type, equipment name, a using unit and a using place;
and the relation establishing module is used for matching the entity equipment information with the equipment ledger with the equipment object model and establishing the relation between the equipment object model and the entity equipment.
According to a third aspect of the embodiments of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method for associating a device object model with a physical device in any of the embodiments described above.
According to a fourth aspect of embodiments of the present disclosure, there is provided an electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the steps of the method of associating a device object model with a physical device in any of the above embodiments via execution of the executable instructions.
The technical scheme provided by the embodiment of the disclosure can comprise the following beneficial effects:
in one embodiment of the disclosure, through the method, on one hand, an equipment object model is built according to a process parameter library, an abnormal code dictionary and a PLC point table of entity equipment, so that a standardized equipment object model is built by referring to instantiation data, and the accuracy of the equipment object model is improved; on the other hand, through matching the entity equipment information with the equipment account with the equipment object model, the association between the equipment object model and the entity equipment is realized, the association degree of the equipment object model and the entity equipment matching is improved, and the reusability of the model is further enhanced.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.
FIG. 1 schematically illustrates a flow chart of steps of a method of associating a device object model with an entity device in an exemplary embodiment of the present disclosure;
FIG. 2 schematically illustrates a process diagram of modeling of a plant object model in an exemplary embodiment of the present disclosure;
FIG. 3 schematically illustrates functional block diagrams of modeling of equipment object models in an exemplary embodiment of the present disclosure;
FIG. 4 schematically illustrates a schematic design of modeling of an equipment object model in an exemplary embodiment of the present disclosure;
FIG. 5 schematically illustrates a data flow diagram of modeling of an equipment object model in an exemplary embodiment of the present disclosure;
FIG. 6 schematically illustrates a block diagram of an apparatus for associating a device object model with a physical device in an exemplary embodiment of the present disclosure;
FIG. 7 schematically illustrates a program product schematic in an exemplary embodiment of the present disclosure;
fig. 8 schematically illustrates a schematic diagram of an electronic device in an exemplary embodiment of the disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.
In this example embodiment, a method for associating an equipment object model with entity equipment is provided first. Referring to what is shown in fig. 1, the method may include: step S101 to step S104.
Wherein, step S101: constructing a database according to a process parameter library, an abnormal code dictionary and a PLC point table of the entity equipment; the technical parameters in the technical parameter library are defined technical parameters when the entity equipment leaves the factory, and the PLC point table at least comprises a PLC name, an address, acquisition frequency, a PLC substation and a unit.
Step S102: establishing an equipment object model according to the database; wherein, the equipment object model at least comprises: device structure partitioning, device attributes, exception code types, and reporting ledger templates.
Step S103: acquiring entity equipment information, and importing an equipment ledger to obtain the entity equipment information with the equipment ledger; the entity equipment information at least comprises equipment type, equipment name, a using unit and a using place.
Step S104: and matching the entity equipment information with the equipment ledger with the equipment object model, and establishing a connection between the equipment object model and the entity equipment.
By the method, on one hand, the equipment object model is built according to the process parameter library, the abnormal code dictionary and the PLC point table of the entity equipment, and the standardized equipment object model is built by referring to the instantiation data; on the other hand, through matching the entity equipment information with the equipment account with the equipment object model, the association between the equipment object model and the entity equipment is realized, the association degree of the equipment object model and the entity equipment matching is improved, and the reusability of the model is further enhanced.
Hereinafter, each step of the above-described method in the present exemplary embodiment will be described in more detail with reference to fig. 1, 2, and 3.
In step S101, a database is constructed according to a process parameter library, an anomaly code dictionary and a PLC point table of the entity device; the technical parameters in the technical parameter library are defined technical parameters when the entity equipment leaves the factory, and the PLC point table at least comprises a PLC name, an address, acquisition frequency, a PLC substation and a unit.
Specifically, as shown in fig. 2, with reference to the process parameters of the entity equipment when leaving the factory, the unique identification and the definition of the english name are performed, the process parameters of the entity equipment form a process parameter library, a plurality of PLC points exist in the entity equipment, each point corresponds to a PLC address, and by establishing an OPC connection and an OPC group, the data of the PLC can be read by using an OPC command, and the PLC addresses are uniformly imported into a database for storage, including the PLC name, address, acquisition frequency, PLC substation and unit, and the like. The PLC is a programmable logic controller, the English of the PLC is named as Programmable Logic Controller, the OPC is an OLE for process control, the English of the PLC is named as OLE for Process Control, the OLE is object connection and embedding, and the OLE is an abbreviation of Object Linking and Embedding. The exception code dictionary is a file in which various exception codes are collected. After the process parameter library, the abnormal code dictionary and the PLC point table of the entity equipment are respectively established, a database can be constructed through the process parameter library, the abnormal code dictionary and the PLC point table of the entity equipment, and the constructed database can be used as a basic database, so that the subsequent use is convenient.
In step S102, an equipment object model is built according to the database; wherein, the equipment object model at least comprises: device structure partitioning, device attributes, exception code types, and reporting ledger templates.
Specifically, as shown in fig. 3, the standardized equipment object model is continuously built according to the built database. Specifically, a set of standardized equipment object models is abstracted according to the functions and characteristics of the interrelated investigation equipment (namely entity equipment). The standardized equipment object model at least comprises equipment structure division, equipment attributes, abnormal code types and a report account template.
In one example, as shown in FIG. 3, the device structure partition includes the composition of devices, device attributes including basic attributes, service attributes, and event attributes.
The basic attribute is used for describing the state of the entity device in operation, and may include information such as a device object model name, a device object model type, and a device object model state, for example, the current environmental temperature read by the environmental monitoring device.
The service attribute is used for describing the capability or method of the entity equipment which can be called by the outside, and can comprise the service which can be provided by the outside and is sent by the data acquisition and control instruction.
Event attributes typically contain notification information that needs to be externally sensed and processed, and may include messages or the like of physical device failures or warnings.
In step S103, obtaining entity equipment information, and importing an equipment ledger to obtain the entity equipment information with the equipment ledger; the entity equipment information at least comprises equipment type, equipment name, a using unit and a using place.
Specifically, as shown in fig. 3, after the entity device information is acquired through the entity device management system, the entity device information is imported into the device ledger, so as to obtain the entity device information with the device ledger, that is, obtain the device type, the device name, the using unit and the using place with the corresponding specific content. It should be noted that, the entity device information includes, in addition to the device type, the device name, the usage unit, and the usage location, other basic information, which may be set according to actual situations, and this disclosure does not limit this.
When the entity equipment information is established, the entity equipment needs to be registered, a unique identifier such as equipment identification is allocated to each entity equipment, the entity equipment can be registered through a network and can be registered in other modes, and after the registration is completed, the entity equipment can be identified and accessed through the network.
It should be noted that the type of the apparatus may be generally differentiated according to the application, such as coal mining, etc., and specifically may be selected according to the actual situation, which is not limited by the present disclosure. The equipment name is generally the name, number or code of the equipment, such as a coal cutter, a mining machine, etc., and specifically may be selected according to practical situations, which is not limited in this disclosure. The usage unit is typically a unit or company that uses a certain entity device, and the usage place is typically a working place of the entity device.
In step S104, the entity equipment information with the equipment ledger is matched with the equipment object model, and a connection between the equipment object model and the entity equipment is established.
Specifically, after the entity equipment information with the equipment ledger is obtained, the entity equipment information with the equipment ledger is matched with the equipment object model to establish the connection between the equipment object model and the entity equipment, the equipment object model is associated with the entity equipment, and after the connection is successful, the entity equipment has all contents in the standardized equipment object model, namely, the standardized equipment object model of the entity equipment as shown in any one of fig. 3 is obtained.
It should be noted that, specific ways of matching the entity equipment information with the equipment ledger and the equipment object model, and associating the equipment object model with the entity equipment are described in the following embodiments, which are not described herein.
In one embodiment, the step of building the equipment object model according to the database includes:
extracting entity equipment data information from the database according to the function and the characteristic of the mutual connection of the entity equipment;
establishing the equipment object model based on the entity equipment data information; the entity equipment data information at least comprises process parameter data, abnormal code data and PLC point table data.
Specifically, as shown in fig. 4, when a database is built based on a process parameter library, an abnormal code dictionary and a PLC point table of the entity equipment, and an equipment model is built through the database, the entity equipment data information is screened from the database mainly by utilizing functions and characteristics shared among the entity equipment, and then a standardized equipment model is built based on the screened entity equipment data information. When the entity equipment data information is screened from the database, the process parameter data, the abnormal code data and the PLC point table data can be screened as the entity equipment data information.
In one embodiment, the step of matching the entity device information with the device ledger with the device object model includes:
binding the equipment object model with the entity equipment information with the equipment ledger according to a preset binding relation;
and verifying the preset binding relationship.
In one embodiment, the preset binding relationship is a relationship corresponding to the entity device information determined by matching a device identifier or the device type from the database.
Specifically, when the entity equipment and the equipment object model are associated, the entity equipment information with the equipment ledger and the equipment object model are matched, and in the process of matching the entity equipment information with the equipment ledger and the equipment object model, the entity equipment information with the equipment ledger and the equipment object model are bound according to a preset binding relationship such as equipment identification or equipment type, so that the association degree of the equipment object model and the entity equipment is improved. When connection is established, the equipment object model and the entity equipment are bound through a network, and a preset binding relation is verified so as to know whether the binding is successful or not.
It should be noted that, the preset binding relationship is in the process of matching through information such as device identification or device type. The matching of the entity equipment and the standardized equipment object model can be performed in a character matching mode, for example, the distance between characters is obtained to determine the correlation, and then the entity equipment corresponding to the standardized equipment object model is determined. The distance between the characters is specifically determined to determine the correlation, which can be understood with reference to the prior art, and this disclosure will not be repeated.
When verifying the preset binding relationship, the method can be performed by means of password authentication, digital signature, identity authentication and the like, and the establishment of the preset binding relationship can ensure the stability and safety of connection between the entity equipment and the equipment object model.
After the equipment object model is connected with the entity equipment, the entity equipment data information generated by the entity equipment is transmitted to a server, and after the server analyzes the entity equipment data information, the information is input, so that the data communication between the entity equipment and the equipment object model is completed.
In one embodiment, the step of establishing a connection between the equipment object model and the entity device comprises the following steps:
and updating the equipment object model according to the state information of the actual existence of the entity equipment.
Specifically, after the equipment object model is associated with the entity equipment, the equipment object model needs to be debugged. The standardized equipment object model can be updated according to the actual state information of the entity equipment to form an adjusted equipment object model so as to maintain consistency between the updated equipment object model and the entity equipment.
After the standardized equipment object model is built, the multiplexing rate of the equipment object model is extremely high, the debugging work after association is gradually reduced, the working cost is reduced, and the research and development efficiency is improved.
In one embodiment, the step of updating the equipment object model according to the state information of the actual existence of the entity equipment includes:
and acquiring the state information of the entity equipment through the equipment object model, and sending the state information to a management center so that the management center generates updated information of the equipment object model.
Specifically, when the equipment object model is updated according to the state information of the actual existence of the entity equipment, the equipment object model acquires the state information of the entity equipment in real time through a network, then the state information is fed back to the management center, and the management center generates updated information of the equipment object model according to the state information.
In addition, the management center can also send a control instruction to the entity equipment through the equipment object model so as to realize remote control of the entity equipment. After the equipment object model is updated, the state information of the entity equipment can be synchronously updated in a polling mode, a subscribing/publishing mode and the like.
FIG. 5 is a data flow diagram of modeling of an equipment object model in an exemplary embodiment of the present disclosure.
When the layer 0 data flows, the PLC automation engineer debugs the debug portrait by configuring the equipment standardization library, then carries out attribute binding points through the PLC point table and the process parameter library, releases the portrait after the attribute binding points, and then feeds back to the user.
When the data is in the top data flow, the PLC automation engineer processes the data of the image debugging binding points, organizes the data and feeds the data back to the user.
The disclosure is further illustrated by example 1 below.
Example 1: taking a coal mining machine in use in a coal mine as an example, the equipment name is as follows: no. 1 coal mining machine
Step 1: and importing a PLC point table. And (5) importing all PLC address tables of the No. 1 coal mining machine.
Step 2: the method comprises the steps of establishing a standardized equipment object model of a coal cutter, and defining a standardized equipment object model of a coal cutter class by combining actual physical structures of a plurality of coal cutter equipment of different models, wherein the standardized equipment object model comprises equipment structure division (divided into a traction part, a cutting part and an electric part) of the coal cutter class, equipment attributes (divided into basic attributes, service attributes and event attributes) of the coal cutter class, abnormal code types, report account templates and the like.
Step 3: the specific information about the No. 1 coal mining machine in the synchronous equipment management system-equipment ledger comprises information such as equipment classification, equipment name, use units, use places and the like and is uniquely coded in the equipment management system.
Step 4: and establishing a connection. And carrying out one-to-one association on the entity equipment 1# coal cutter and the standardized equipment object model class of the coal cutter, carrying out data unidirectional synchronization, and after the association relation is established, obtaining information such as equipment attribute, abnormal code type, report account template and the like which are the same as the standardized equipment object model of the coal cutter by the entity equipment 1# coal cutter.
Step 5: debugging the equipment object model. And carrying out small adjustment on the contents endowed to the entity equipment by standardization such as equipment attribute, abnormal code type, report account template and the like according to the actual condition.
It should be noted that although the steps of the methods of the present disclosure are illustrated in the accompanying drawings in a particular order, this does not require or imply that the steps must be performed in that particular order or that all of the illustrated steps be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc. In addition, it is also readily understood that these steps may be performed synchronously or asynchronously, for example, in a plurality of modules/processes/threads.
Further, in this example embodiment, an apparatus for associating an equipment object model with entity equipment is also provided. Referring to fig. 6, an apparatus 200 may include a build module 201, a model build module 202, an acquisition module 203, and a relationship build module 204.
Wherein: a construction module 201, configured to construct a database according to a process parameter library, an abnormal code dictionary and a PLC point table of the entity device; the technical parameters in the technical parameter library are defined technical parameters when the entity equipment leaves the factory, and the PLC point table at least comprises a PLC name, an address, acquisition frequency, a PLC substation and a unit;
a model building module 202, configured to build an equipment object model according to the database; wherein, the equipment object model at least comprises: device structure division, device attributes, abnormal code types and report account templates;
the acquiring module 203 is configured to acquire entity equipment information, and import an equipment ledger to obtain the entity equipment information with the equipment ledger; the entity equipment information at least comprises equipment type, equipment name, a using unit and a using place;
and the relationship establishing module 204 is configured to match the entity equipment information with the equipment ledger with the equipment object model, and establish a relationship between the equipment object model and the entity equipment.
In one embodiment, the apparatus further comprises:
the extraction module is used for extracting entity equipment data information from the database according to the function and the characteristic of the mutual connection of the entity equipment;
establishing the equipment object model based on the entity equipment data information; the entity equipment data information at least comprises process parameter data, abnormal code data and PLC point table data.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied. The components shown as modules or units may or may not be physical units, may be located in one place, or may be distributed across multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the objectives of the disclosed solution. Those of ordinary skill in the art will understand and implement the present application without undue burden.
In an exemplary embodiment of the disclosure, a computer readable storage medium is further provided, on which a computer program is stored, where the program is configured to implement the steps of the method for associating a device object model with a physical device according to any one of the embodiments described above when executed by a processor. In some possible embodiments, the aspects of the present application may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the present application as described in the above description of the method of associating a device object model with a physical device, when said program product is run on the terminal device.
Referring to fig. 7, a program product 300 for implementing the above-described method according to an embodiment of the present application is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present application is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable storage medium may also be any readable medium that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
In an exemplary embodiment of the present disclosure, an electronic device is also provided, which may include a processor, and a memory for storing executable instructions of the processor. Wherein the processor is configured to perform the steps of the method of associating a device object model with a physical device in any of the above embodiments via execution of the executable instructions.
Those skilled in the art will appreciate that the various aspects of the application may be implemented as a system, method, or program product. Accordingly, aspects of the application may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.
An electronic device 600 according to this embodiment of the application is described below with reference to fig. 8. The electronic device 600 shown in fig. 8 is merely an example, and should not be construed as limiting the functionality and scope of use of embodiments of the present application.
As shown in fig. 8, the electronic device 600 is in the form of a general purpose computing device. Components of electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one memory unit 620, a bus 630 connecting the different system components (including the memory unit 620 and the processing unit 610), a display unit 640, etc.
Wherein the storage unit stores program code that is executable by the processing unit 610 such that the processing unit 610 performs the steps according to various exemplary embodiments of the present application described in the above-mentioned method section of associating a device object model with a physical device of the present description. For example, the processing unit 610 may perform the steps as shown in fig. 1.
The memory unit 620 may include readable media in the form of volatile memory units, such as Random Access Memory (RAM) 6201 and/or cache memory unit 6202, and may further include Read Only Memory (ROM) 6203.
The storage unit 620 may also include a program/utility 6204 having a set (at least one) of program modules 6205, such program modules 6205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
Bus 630 may be a local bus representing one or more of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or using any of a variety of bus architectures.
The electronic device 600 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 600, and/or any device (e.g., router, modem, etc.) that enables the electronic device 600 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 650. Also, electronic device 600 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 660. The network adapter 660 may communicate with other modules of the electronic device 600 over the bus 630. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 600, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a usb disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, or a network device, etc.) to perform the method for associating the device object model with the entity device according to the embodiments of the present disclosure.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (10)
1. A method for associating a device object model with an entity device, comprising:
constructing a database according to a process parameter library, an abnormal code dictionary and a PLC point table of the entity equipment; the technical parameters in the technical parameter library are defined technical parameters when the entity equipment leaves the factory, and the PLC point table at least comprises a PLC name, an address, acquisition frequency, a PLC substation and a unit;
establishing an equipment object model according to the database; wherein, the equipment object model at least comprises: device structure division, device attributes, abnormal code types and report account templates;
acquiring entity equipment information, and importing an equipment ledger to obtain the entity equipment information with the equipment ledger; the entity equipment information at least comprises equipment type, equipment name, a using unit and a using place;
and matching the entity equipment information with the equipment ledger with the equipment object model, and establishing a connection between the equipment object model and the entity equipment.
2. The method for associating an equipment object model with an entity device according to claim 1, wherein the step of establishing the equipment object model according to the database comprises:
extracting entity equipment data information from the database according to the function and the characteristic of the mutual connection of the entity equipment;
establishing the equipment object model based on the entity equipment data information; the entity equipment data information at least comprises process parameter data, abnormal code data and PLC point table data.
3. The method for associating an equipment object model with an entity device according to claim 1, wherein the step of matching the entity device information with the equipment ledger with the equipment object model comprises:
binding the equipment object model with the entity equipment information with the equipment ledger according to a preset binding relation;
and verifying the preset binding relationship.
4. The method for associating an equipment object model with entity equipment according to claim 3, wherein the preset binding relationship is a relationship corresponding to the entity equipment information determined by matching an equipment identifier or the equipment type from the database.
5. The method of associating an equipment object model with an entity device according to claim 1, wherein the step of establishing a connection between the equipment object model and the entity device comprises:
and updating the equipment object model according to the state information of the actual existence of the entity equipment.
6. The method for associating an equipment object model with an entity device according to claim 5, wherein the step of updating the equipment object model according to the status information of the entity device actually existing comprises:
and acquiring the state information of the entity equipment through the equipment object model, and sending the state information to a management center so that the management center generates updated information of the equipment object model.
7. The method of associating a device object model with an entity device of claim 1, wherein the device attributes include a base attribute, a service attribute, and an event attribute; the basic attributes are used for describing the running state of the entity equipment, and comprise equipment object model names, equipment object model types and equipment object model states; the service attribute is used for describing the capability or method of the entity equipment which can be called by the outside, and comprises a service which can be provided by the outside and is sent by a data acquisition and control instruction; the event attributes contain notification information that needs to be externally perceived and processed, including messages of physical device failure or warning.
8. An apparatus for associating a device object model with a physical device, comprising:
the construction module is used for constructing a database according to the process parameter library, the abnormal code dictionary and the PLC point table of the entity equipment; the technical parameters in the technical parameter library are defined technical parameters when the entity equipment leaves the factory, and the PLC point table at least comprises a PLC name, an address, acquisition frequency, a PLC substation and a unit;
the model building module is used for building an equipment object model according to the database; wherein, the equipment object model at least comprises: device structure division, device attributes, abnormal code types and report account templates;
the device comprises an acquisition module, a verification module and a verification module, wherein the acquisition module is used for acquiring entity equipment information and importing equipment ledgers to obtain the entity equipment information with the equipment ledgers; the entity equipment information at least comprises equipment type, equipment name, a using unit and a using place;
and the relation establishing module is used for matching the entity equipment information with the equipment ledger with the equipment object model and establishing the relation between the equipment object model and the entity equipment.
9. A computer readable storage medium having stored thereon a computer program, characterized in that the program when executed by a processor realizes the steps of the method for associating a device object model with a physical device according to any of claims 1-7.
10. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the steps of the method of associating an equipment object model with a physical equipment of any one of claims 1-7 via execution of the executable instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311059586.4A CN116774645A (en) | 2023-08-22 | 2023-08-22 | Method, device, medium and equipment for associating equipment object model with entity equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311059586.4A CN116774645A (en) | 2023-08-22 | 2023-08-22 | Method, device, medium and equipment for associating equipment object model with entity equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116774645A true CN116774645A (en) | 2023-09-19 |
Family
ID=87994876
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311059586.4A Pending CN116774645A (en) | 2023-08-22 | 2023-08-22 | Method, device, medium and equipment for associating equipment object model with entity equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116774645A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109389326A (en) * | 2018-11-05 | 2019-02-26 | 国网四川省电力公司 | Objectification modeling method, equipment and system towards monitor event |
| CN113259155A (en) * | 2021-04-21 | 2021-08-13 | 京东数字科技控股股份有限公司 | Access method, device, gateway, medium and electronic equipment of Internet of things equipment |
| CN114202304A (en) * | 2021-12-06 | 2022-03-18 | 中国南方电网有限责任公司超高压输电公司南宁监控中心 | Intelligent monitoring processing method and system for power grid faults |
| CN114218724A (en) * | 2021-11-30 | 2022-03-22 | 国网北京市电力公司 | Model construction method, device and system for power secondary system and storage medium |
| CN114253228A (en) * | 2021-11-22 | 2022-03-29 | 中国科学院软件研究所 | Industrial equipment object modeling method and device based on digital twinning |
| WO2022247519A1 (en) * | 2021-05-26 | 2022-12-01 | 广州地铁集团有限公司 | Object model device management method and apparatus, device, system, and storage medium |
| CN115793559A (en) * | 2022-11-29 | 2023-03-14 | 厦门四信通信科技有限公司 | Configuration method and device of PLC acquisition point table, intelligent gateway, equipment and medium |
| CN116244387A (en) * | 2023-02-27 | 2023-06-09 | 上海太美数字科技有限公司 | Entity relationship construction method, device, electronic equipment and storage medium |
| CN116257926A (en) * | 2023-05-09 | 2023-06-13 | 宇动源(北京)信息技术有限公司 | BIM-based Internet of things data binding method, device, equipment and storage medium |
-
2023
- 2023-08-22 CN CN202311059586.4A patent/CN116774645A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109389326A (en) * | 2018-11-05 | 2019-02-26 | 国网四川省电力公司 | Objectification modeling method, equipment and system towards monitor event |
| CN113259155A (en) * | 2021-04-21 | 2021-08-13 | 京东数字科技控股股份有限公司 | Access method, device, gateway, medium and electronic equipment of Internet of things equipment |
| WO2022247519A1 (en) * | 2021-05-26 | 2022-12-01 | 广州地铁集团有限公司 | Object model device management method and apparatus, device, system, and storage medium |
| CN114253228A (en) * | 2021-11-22 | 2022-03-29 | 中国科学院软件研究所 | Industrial equipment object modeling method and device based on digital twinning |
| CN114218724A (en) * | 2021-11-30 | 2022-03-22 | 国网北京市电力公司 | Model construction method, device and system for power secondary system and storage medium |
| CN114202304A (en) * | 2021-12-06 | 2022-03-18 | 中国南方电网有限责任公司超高压输电公司南宁监控中心 | Intelligent monitoring processing method and system for power grid faults |
| CN115793559A (en) * | 2022-11-29 | 2023-03-14 | 厦门四信通信科技有限公司 | Configuration method and device of PLC acquisition point table, intelligent gateway, equipment and medium |
| CN116244387A (en) * | 2023-02-27 | 2023-06-09 | 上海太美数字科技有限公司 | Entity relationship construction method, device, electronic equipment and storage medium |
| CN116257926A (en) * | 2023-05-09 | 2023-06-13 | 宇动源(北京)信息技术有限公司 | BIM-based Internet of things data binding method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112507027B (en) | Kafka-based incremental data synchronization method, device, equipment and medium | |
| US8451753B2 (en) | Systems and methods for the configuration of substation remote terminals with a central controller | |
| CN111683066B (en) | Heterogeneous system integration method, heterogeneous system integration device, computer equipment and storage medium | |
| CN111857777B (en) | System updating method and device based on double-core intelligent ammeter and computer equipment | |
| KR101453671B1 (en) | Integrated interface system for monitoring and controling electric power system | |
| CN106371869B (en) | IEC61850 configuration software implementation method for bay level equipment of intelligent substation | |
| CN101699403A (en) | Method for graphically installing distributed system | |
| CN105760272A (en) | Monitoring background service customization method based on plug-in and system based on method | |
| CN111178849A (en) | Linear process engine implementation method, device, equipment and storage medium | |
| CN111737227A (en) | Data modification method and system | |
| US20200092126A1 (en) | Building automation system providing for integration of subsystems | |
| CN114448802A (en) | Gateway configuration method and device, electronic equipment and storage medium | |
| WO2005124571A1 (en) | Mutual access method of data and mutual access system of data | |
| CN111212093A (en) | Data processing system and control device | |
| CN116774645A (en) | Method, device, medium and equipment for associating equipment object model with entity equipment | |
| CN114741056A (en) | Internet of things management platform based on big data and cloud computing | |
| CN115118587A (en) | Method and device for creating connector | |
| CN105335145A (en) | Operation result processing method, device and system | |
| CN1932760B (en) | System and method for execution of application program | |
| CN114363202A (en) | Terminal access state monitoring method, device, system, electronic equipment and medium | |
| CN113434473A (en) | Distributed log processing method, device, medium and electronic equipment | |
| KR20200081657A (en) | Platform of Smart Factory | |
| KR101888792B1 (en) | Method for data communication and system comprising the same | |
| CN113449035B (en) | Data synchronization method, device, computer equipment and readable storage medium | |
| CN111107154B (en) | Data reporting method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |