CN114510219B - Industrial object model based on middleware of Internet of things and implementation method thereof - Google Patents
Industrial object model based on middleware of Internet of things and implementation method thereof Download PDFInfo
- Publication number
- CN114510219B CN114510219B CN202210411759.3A CN202210411759A CN114510219B CN 114510219 B CN114510219 B CN 114510219B CN 202210411759 A CN202210411759 A CN 202210411759A CN 114510219 B CN114510219 B CN 114510219B
- Authority
- CN
- China
- Prior art keywords
- data
- object model
- information
- equipment
- service
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The invention claims an industrial object model based on an Internet of things middleware and an implementation method thereof, wherein the model comprises a data layer, a service layer and a display layer, various equipment configuration information is synchronized to an object model management service cluster by an equipment/protocol access service cluster, and then the equipment configuration information is unified into the industrial object model for management, so that abstract management and equipment variable acquisition and control of similar products are realized, and the problems of non-uniform attribute definition and large development and butt joint difficulty when a plurality of terminal equipment/facilities interact with a service end in the existing industrial scene are solved. The object model implementation method is described from four dimensions of identity, attribute, event and service, terminal equipment or facilities are uniformly accessed into the middleware of the Internet of things according to the object model method, the middleware performs data cleaning or calculation on data and finally provides the data to a third-party platform to complete data collection processing, and the object model implementation method can be applied to equipment and facility model definition of various industrial scenes, can more conveniently implement equipment and object association and has wide application prospect.
Description
Technical Field
The invention relates to an industrial object model based on an Internet of things middleware and an implementation method thereof, and provides a standard data model for realizing Internet of things data collection in an industrial scene; belongs to the technical field of the correlation of the Internet of things.
Background
The continued maturation of the internet and traditional telecommunications networks provides the infrastructure for ubiquitous terminal equipment and infrastructure networking. With the development of information technology, the internet of things industry has been getting more and more fierce in recent years, and when various terminal devices or facilities are networked, because respective attributes of different types of devices are different, in order to solve the problem, most companies generally define a data configuration structure for different types of devices when configuring the device attributes. The processing mode is adopted under the condition of multiple equipment types, the difficulty of development and third-party docking is high, the data analysis function needs to be developed again when one type is added, and the development cost is high and the efficiency is low.
In view of the above problems, there is a need for a method capable of uniformly describing the attributes/behaviors of devices or facilities, so as to reduce the access difficulty of the devices and facilities.
Disclosure of Invention
Aiming at solving the defects of the prior art, the invention aims to provide an industrial object model based on an internet of things middleware and an implementation method thereof, aiming at the problems of non-uniform attributes and high development and docking difficulty when a plurality of terminal devices/facilities interact with a server side in the prior industrial scene.
In order to achieve the above object, the present invention adopts the following technical solutions:
the invention discloses an industrial object model based on middleware of the Internet of things, wherein the overall architecture of the industrial object model comprises a data layer, a service layer and a display layer; the service layer is a core layer and is used for calling the data layer to store data and providing a data query, addition, modification and deletion functional interface for the display layer; the data layer is used for storing and caching data and providing a data storage function for the service layer; the display layer provides WEB interface display and operation functions for the service layer and is used for providing industrial object model management, model-associated equipment management, rule management, historical data setting and viewing and API interface configuration and viewing in a WEB interface mode.
Preferably, the aforementioned data layer includes: a structure database, a time sequence database and a cache database; the time sequence database stores variable data according to the characteristics of the data of the Internet of things, the structure database is used for configuring data, and the cache database is used for improving the data reading and writing performance and realizing cache data acquisition.
Still preferably, the aforementioned structure database is used for storing configuration class data, such as industrial object model structure information; the time sequence database is used for storing collected data reported by the equipment/protocol service, such as temperature information collected and reported every second by the sensor equipment; the cache database is used for storing frequently called data so as to improve the viewing efficiency, such as model variable attributes, alarm triggering conditions and other information.
Preferably, the service layer includes a device/protocol access service cluster and a physical model management service cluster, the device/protocol access service cluster synchronizes various device configuration information to the physical model management service cluster, and the physical model management service cluster unifies the device configuration information into an industrial physical model for management.
More preferably, the object model management service cluster includes: the system comprises an object model management module, an API (application program interface) module, a rule engine module and a historical data module; the object model management module provides an object model conversion interface for the equipment/protocol access service, converts configuration information and real-time or historical data information reported by the industrial Internet of things gateway, the MQTT direct-connected equipment and the soft gateway into a unified object model structure, and calls an interface provided by the API interface module to provide data to a third-party application platform to complete data docking; when the object model management module performs real-time or historical data information conversion, if the data is configured with an operation rule or an event rule, the rule engine module is called to complete operation, and then the value after operation is returned to the object model management module; if the data is set to be in a storage state, a historical data module is called to store the data to a time sequence database, and meanwhile, the historical data module also provides a historical data query interface for the third-party application platform.
The invention also discloses an implementation method of the industrial object model based on the middleware of the Internet of things, which comprises the following steps:
s1, industrial object model definition: defining an industrial object model from four aspects of identity information, attribute information, event information and service information;
the identity information is used for defining the version, the number and the name of the industrial object model; including field version: indicating version number, code: representation model unique number, name: self-defining the name of the model;
the attribute information is used for defining variable information in the industrial object model and comprises the following fields: unique identification of variable, name: variable name, accessMode: operation type, r: read-only, w: write only, rw: reading and writing; operationType: the type of operation; source: variable source, string form; DataType describes a data type definition, where type: data types, respectively, are pool, int, long, float, double, string; specs.min is the minimum measuring range; max is the maximum measuring range; pieces. unit: represents a unit; decimal: represents a decimal place; canal. inputformula: inputting a formula; output of rules. outputformula: outputting a formula;
the event information is used for defining alarm and message information in the industrial object model and comprises the following fields: an event unique identifier; name: an event name; operationType: the type of operation; eventType: event type, waring indicates alarm, info indicates message; source: event source, string form; tiger status: a trigger state; event level unique identifier; name: an event level name; value: an event level; level is corresponding to level info.identifier value; conditions: defining conditions; rules. trigermsg: a trigger message;
the service information is used for defining service calls in the industrial object model and comprises the following fields: an identifier: a service unique identifier; name: a service name; a service mode firmware field; operationType: a service operation type; callType: a service letter name; source: service source, string form; input is defined for service input parameters, and comprises an identifier: inputting a unique identifier of a parameter, name: input parameter name, datatype: data type, datatype.specs.min: minimum range, datatype.specs.max: maximum range, datatype.specs.unit: the units are identified.
S2, interface of device/protocol access service cluster to object model: adding an industrial equipment configuration template into the equipment/protocol access service cluster, converting the equipment attribute into an industrial object model form, and calling an interface to synchronize data to the object model management service cluster;
s3, management of object models: all the industrial object models synchronized by the equipment/protocol access service cluster are managed in a unified way; when some variables of equipment/facilities related to the model report data, the object model management service cluster judges whether real-time data is stored in a database according to whether the variables are set to be stored or not, if the variables are judged to be set to be stored, the real-time data of the variables are stored in a time sequence database, and expired data is automatically cleared after the expiration according to the set effective time length of data storage; if the variable is judged not to be stored, the variable can only use the real-time data function;
s4, equipment management based on object model: and uniformly managing equipment variable information, equipment states and data in the equipment synchronized to the object model management service cluster, checking and reversely controlling and issuing, and uploading the equipment states to the middleware of the Internet of things through a protocol according to data acquired by actual equipment.
Further preferably, in the foregoing step S1, the identity information is used to define the name, number, source, type and extensible information of the object model itself; the attribute information is used for defining specific information and states of the equipment, and the operation types are divided into read-only types, write-only types and read-write types; the event information is used for defining information actively reported to the cloud end when the equipment runs, and comprises information needing to be sensed and processed by the outside, alarm and fault; the service information is used for defining instructions or methods which can be called by the equipment from the outside, and complex business logic is realized.
Still more preferably, in the step S2, the specific process of data synchronization is as follows:
(1) the object model management service cluster analyzes identity information, attribute information, event information and service information according to the received JSON data;
(2) judging the access service source of the model according to the identity information, and finishing classification of data according to the source when the data are put in storage;
(3) judging according to the analysis results of the attribute information, the event information and the service information; if the model information is not stored in the database, storing the information into a warehouse; if the data exists in the database, comparing whether the data in the database is the same as the synchronous model information or not, if not, updating, and if not, not processing; if the synchronized template identity information exists in the database but the attribute information, the event information and the service information do not exist in the synchronized data, the information is deleted by the equipment/protocol access service, and the corresponding information stored in the object model management service cluster needs to be removed, so that the data consistency is ensured.
Still further preferably, the service sources include: the system comprises an industrial Internet of things gateway, MQTT direct connection equipment and a soft gateway.
Still further preferably, the protocol in the foregoing step S4 includes: one or more of http, mqtt, OPC, and Modbus.
The invention has the advantages that:
(1) the invention discloses an industrial object model based on middleware of the Internet of things, which comprises a data layer, a service layer and a display layer, wherein the data layer selects a time sequence database for variable data storage according to the characteristics of data of the Internet of things, a structure database (mysql) is adopted for configuration data, and the cache database is used for storing for caching data acquisition so as to improve the data reading and writing performance; the device/protocol access service cluster synchronizes various device configuration information to the object model management service, the object model management service can unify the device configuration information into an industrial object model for management, abstract management of similar products and collection and control of device variables are achieved, and the problems that attribute definition is not uniform and development and butt joint difficulty is large when a plurality of terminal devices/facilities interact with a server side in the existing industrial scene are solved.
(2) The object model realization method of the invention describes what a product entity is, what can be done, which capabilities are provided externally and the like from four dimensions of identity, attribute, event and service, thereby greatly reducing development and docking difficulty.
Drawings
FIG. 1 is an overall framework diagram of an Internet of things middleware based industrial object model of the present invention;
FIG. 2 is a dimension schematic diagram of an industrial object model implementation method based on middleware of the Internet of things;
fig. 3 is an expanded example diagram of four dimensions of the industrial object model implementation method based on the middleware of the internet of things.
Detailed Description
The invention is described in detail below with reference to the figures and the embodiments.
Example 1
The embodiment discloses an industrial model based on middleware of the internet of things, and as can be seen from fig. 1, the overall architecture of the industrial model comprises a data layer, a service layer and a display layer.
The data layer is used for storing and caching data and providing a data storage function for the service layer. The method specifically comprises the following steps: a structure database, a time sequence database and a cache database; the structure database is used for storing configuration class data, such as industrial object model structure information; the time sequence database is used for storing collected data reported by the equipment/protocol service, such as temperature information collected and reported every second by the sensor equipment; the cache database is used for storing frequently called data so as to improve the viewing efficiency, such as model variable attributes, alarm triggering conditions and other information.
The service layer is a core layer and is used for calling the data layer to store data and providing a data query, addition, modification and deletion function interface for the display layer. The system comprises an equipment/protocol access service cluster and an object model management service cluster, wherein the equipment/protocol access service cluster synchronizes various equipment configuration information to the object model management service cluster, and the object model management service cluster unifies the equipment configuration information into an industrial object model for management. Specifically, the object model management service cluster comprises: the system comprises an object model management module, an API (application program interface) module, a rule engine module and a historical data module; the object model management module provides an object model conversion interface for the equipment/protocol access service, converts configuration information and real-time or historical data information reported by the industrial Internet of things gateway, the MQTT direct-connected equipment and the soft gateway into a unified object model structure, and calls an interface provided by the API interface module to provide data to a third-party application platform to complete data docking; when the object model management module carries out real-time or historical data information conversion, if the data is provided with an operation rule or an event rule, the rule engine module is called to complete operation, and the value after operation is returned to the object model management module; if the data is set to be in a storage state, a historical data module is called to store the data in a time sequence database, and meanwhile, the historical data module also provides a historical data query interface for a third-party application platform.
The display layer provides WEB interface display and operation functions for the service layer and is used for providing industrial object model management, model-associated equipment management, rule management, historical data setting and viewing and API interface configuration and viewing in a WEB interface mode.
Example 2
The embodiment discloses an implementation method of an industrial object model based on an internet of things middleware, which specifically comprises the following steps:
s1, industrial object model definition:
referring to fig. 2, the present invention defines an industrial object model from four aspects of identity information, attribute information, event information and service information.
The identity information Profile field is used for defining the name, number, source, type and extensible information of the object model, and comprises the following fields: indicating version number, code: representation model unique number, name: and (4) self-defining the name of the model.
Attribute information properties defines specific information and states of equipment, wherein a key field identifier is a unique identifier of a variable and is unique in the whole industrial object model; name: variable name, accessMode: operation type, r: read-only, w: write only, rw: reading and writing; operationType: the type of operation; source: a source of variables, in the form of a string, to distinguish from which device/facility the information came from accessing the service; DataType describes a data type definition, where type: the data types are respectively boul, int, long, float, double and string; min is the minimum range; max is the maximum range; pieces. unit: represents a unit; decimal: represents a decimal place; canal. inputformula: inputting a formula; output of rules. outputformula: and outputting the formula.
The event information events defines information which is actively reported to the cloud end when the equipment runs, generally comprises information which needs to be sensed and processed by the outside and alarm, and can flexibly define events by configuring a rule mode; the contained field has identifier: an event unique identifier; name: an event name; operationType: the type of operation; eventType: event type, waring indicates alarm, info indicates message; source: event source, string form; tiger status: a trigger state; an event level unique identifier; name: an event level name; value: an event level; level is corresponding to level info.identifier value; conditions: defining conditions; triles msg: a message is triggered. When the event trigger condition is set, multivariable AND/OR can be supported, and meanwhile, linkage action can be set; when the condition reaches the triggering condition, if the linkage action is set, the linkage can be triggered, a control instruction is issued for the data associated with the linkage action, and the whole process can complete alarm triggering linkage; for example, when the temperature exceeds a set threshold value, an alarm lamp is turned on, and alarm linkage setting is adopted to realize the operation.
The service information services defines instructions or methods which can be called by the equipment from the outside, can realize more complex service logics, and can also set input and output variables for the service. Contains the following fields: identifier: a service unique identifier; name: a service name; a service mode firmware field; operationType: a service operation type; callType: a service letter name; source: service source, string form; input is defined for service input parameters, and comprises an identifier: inputting a unique identifier of a parameter, name: input parameter name, datatype: data type, datatype.specs.min: minimum range, datatype.specs.max: maximum range, datatype.specs.unit: the units are identified.
For a better understanding and implementation of the present invention, the following develops an example of the definition structure of the industrial object model described above with reference to fig. 3:
{
"profile": {
"version": 1.0",/, version number
"code", "cfg _10000123",/"model number, the only one in the system
"name": Pro1001-1 "/" model name
},
"properties": [
{
"identifier": er823j23j9823h ",/' variable uniquely identifies and uniquely identifies/in the object model
"name": temperature "/. variable name
"accessMode": r "/" operation type, r: read-only, w: write only, rw: reading and writing pick & pick
"operationType": 1,/"operation type, 1 Add new, 2 Modify, 3 delete
"source", "gatewaybox",/"variable source
"dataType": {
"type": float "/" data type: bool, int, Long, float, double, string
"specs": {
"min": 0",/' minimum range
"max": 100",/" maximum range
Unit: "° c",/. unit: @ |)
"decimal": 2 "/. decimal place:
},
"rules": {
"inputFormula": X/(X +1) ",/' input formula
"outputFormula": X-1 "/" output formula
}
}
}
],
"events": [
{
"identifier": e282123j9823h ",/" event unique identifier, unique within the object model
"name": alarm 001 "/_ event name: -
"operationType": 1,/"operation type, 1 Add new, 2 Modify, 3 delete
"eventType": warning "/" event type; info/warming-
"source", "gatewaybox",/"event source
"tigerstatus": 1",/event status, 1 trigger, 0 elimination
"levelInfo": [
{
"identifier": r282sfj98231 "/' event level unique number
"name": severe ",/" event rating description
"value": 2 "/" event rating
}
],
"rules": [
{
"level", "r28",/"configuration event rank number, corresponding to identifier in levelinfo
"conditions": [
{
"identifier" "," inputData1 "",/"conditionally unique identifier
"name": inputData1 "/' Condition name
"dataType": {
"type": int ",/" conditional variable data type
"threshold value": 10",/, threshold value
"rule": 1 "/" comparison rule, 1: greater than, 2: less than, 3: is equal to ·
}
}
],
"trigerMsg"/"greater than 10 alarm message"/"trigger push message content
}
]
}
],
"services": [
{
"name": server001",/service name
"identifier": s28ew123jdf31 "/' service unique number:
"function mode"/"service mode, reserved field
"operationType": 1,/"operation type, 1 Add new, 2 Modify, 3 delete
"callType",/"callback method name
Source, gatewaybox, service source, and/or
"input": [
{
"identifier" "," inputData1 "",/"variable uniquely numbered
"name": inputData1",/' variable name
"dataType": {
"type" "," int ""/"data type, boul, int, long, float, double, string
"specs": {
"min": 0",/' minimum range
"max": 100",/" maximum range
Unit: "° c",/. unit: @ |)
"decimal": 2 "/. decimal place:
}
}
}
]
}
]
}
s2, interface of device/protocol access service cluster to object model:
generally, the devices are deployed in a cluster manner, for example, an industrial gateway service, an MQTT direct connection service, a protocol parsing service, and the like are all used for configuring devices, and due to various types of industrial scene devices, processing manners and configuration manners of devices of different manufacturers, which are docked by an access layer, may be different. Therefore, when the industrial equipment configuration template is added, an interface is required to be called to synchronize data to the object model management service cluster, and the equipment attribute is converted into an industrial object model form.
The specific conversion process is as follows: and the object model management service cluster module completes analysis according to the received model JSON data and judges whether the model information exists in the database. If the data exists in the database, comparing whether the data in the database is the same as the synchronous model information or not, if so, not processing, and if not, updating; if the synchronized template identity information is judged to exist in the database, but the attribute information, the event information and the service information do not exist in the synchronized data, but do not exist in the database, the information is deleted by the access layer, and the corresponding information stored in the object model management service cluster needs to be removed.
The device/protocol access service cluster configures the association relationship between the device and the template, and simultaneously transmits data to the object model management service cluster by calling the object model management service cluster synchronization interface, and the object model management service cluster associates the device with the object model corresponding to the template to complete the information synchronization of the device.
The specific synchronization process is as follows:
(1) the object model management service cluster analyzes identity information, attribute information, event information and service information according to the received JSON data;
(2) judging access service sources (including industrial Internet of things gateway, MQTT direct connection equipment, soft gateway and the like) of the model according to the identity information, and finishing classification of data according to the sources when the data are put into a warehouse;
(3) judging according to the analysis results of the attribute information, the event information and the service information; if the model information is not stored in the database, storing the information into a warehouse; if the data exists in the database, comparing whether the data in the database is the same as the synchronous model information or not, if not, updating, and if not, not processing; if the synchronized template identity information is judged to exist in the database, but the attribute information, the event information and the service information do not exist in the synchronized data, the information is deleted by the equipment/protocol access service, the corresponding information stored in the object model management service cluster needs to be removed, and the data consistency is ensured.
S3, management of object models:
the method comprises the steps of uniformly managing all industrial object models synchronized by a device/protocol access service cluster, setting whether variables support historical data storage or not by taking the object models as units, and specifying the effective storage duration of the historical data. When some variables of equipment/facilities related to the model report data, the object model management service cluster judges whether real-time data is stored in a database according to whether the variables are set to be stored or not, if the variables are judged to be set to be stored, the real-time data of the variables are stored in a time sequence database, and expired data is automatically cleared after the expiration according to the set effective time length of data storage; if the variable is judged not to be stored, the variable can only use the real-time data function.
S4, equipment management based on object model:
and after the data is cleaned by the physical model management service cluster, the data is provided for an external access interface according to different protocols (http, mqtt, OPC, Modbus and the like) for being called by a third party by calling an API interface module.
In conclusion, the industrial object model based on the middleware of the internet of things and the implementation method thereof realize abstract management of similar products and acquisition and control of equipment variables, solve the problems of non-uniform attribute definition and high development and butt joint difficulty when a plurality of terminal equipment/facilities interact with a server in the existing industrial scene, and can be applied to equipment and facility model definition in various industrial scenes, thereby more conveniently realizing equipment internet of things and having wide application prospects.
The foregoing illustrates and describes the principles, general features, and advantages of the present invention. It should be understood by those skilled in the art that the above embodiments do not limit the present invention in any way, and all technical solutions obtained by using equivalent alternatives or equivalent variations fall within the scope of the present invention.
Claims (7)
1. An industrial object model based on middleware of the Internet of things is characterized in that the overall architecture comprises a data layer, a service layer and a display layer;
the service layer is a core layer and is used for calling the data layer to store data and providing a data query, addition, modification and deletion functional interface for the display layer;
the service layer comprises a device/protocol access service cluster and a physical model management service cluster, the device/protocol access service cluster synchronizes various device configuration information to the physical model management service cluster, and the physical model management service cluster unifies the device configuration information into an industrial physical model for management; the object model management service cluster includes: the system comprises an object model management module, an API (application program interface) module, a rule engine module and a historical data module; the object model management module provides an object model conversion interface for the device/protocol access service, converts configuration information and real-time or historical data information reported by the industrial Internet of things gateway, the MQTT direct connection device and the soft gateway into a unified object model structure, and calls an interface provided by the API interface module to provide data to a third-party application platform to complete data docking; when the object model management module carries out real-time or historical data information conversion, if the data is provided with an operation rule or an event rule, the rule engine module is called to complete operation, and the value after operation is returned to the object model management module; if the data is set to be in a storage state, calling a historical data module to store the data into a time sequence database, and simultaneously providing a historical data query interface for a third-party application platform by the historical data module;
the data layer is used for storing and caching data and providing a data storage function for the service layer;
the display layer provides WEB interface display and operation functions for the service layer and is used for providing industrial object model management, model-associated equipment management, rule management, historical data setting and viewing and API interface configuration and viewing in a WEB interface mode.
2. The internet of things middleware-based industrial object model of claim 1, wherein the data layer comprises: a structure database, a time sequence database and a cache database.
3. The internet of things middleware-based industrial object model as claimed in claim 2, wherein the structure database is used for storing configuration class data; the time sequence database is used for storing the collected data reported by the equipment/protocol service; the cache database is used for storing frequently called data.
4. The method for realizing the industrial object model based on the middleware of the Internet of things according to any one of claims 1 to 3, characterized by comprising the following steps:
s1, industrial object model definition: defining an industrial object model from four dimensions of identity information, attribute information, event information and service information;
s2, interface of device/protocol access service cluster to object model: adding an industrial equipment configuration template into the equipment/protocol access service cluster, converting the equipment attribute into an industrial object model form, and calling an interface to synchronize data to the object model management service cluster;
the specific process of data synchronization is as follows:
(1) the object model management service cluster analyzes identity information, attribute information, event information and service information according to the received model JSON data;
(2) judging the access service source of the model according to the identity information, and finishing classification of data according to the source when the data are put in storage;
(3) judging according to the analysis results of the attribute information, the event information and the service information; if the model information is not stored in the database, storing the information into a warehouse; if the data exists in the database, comparing whether the data in the database is the same as the synchronous model information or not, if not, updating, and if not, not processing; if the synchronized template identity information exists in the database but the attribute information, the event information and the service information do not exist in the synchronized data, the information is deleted by the equipment/protocol access service, and the corresponding information stored in the object model management service cluster needs to be removed, so that the data consistency is ensured;
s3, management of object models: uniformly managing all the industrial object models synchronized by the device/protocol access service cluster; when some variables of equipment/facilities related to the model report data, the object model management service cluster judges whether to store the real-time data into the database according to whether the variables are set to be stored or not, if the variables are judged to be set to be stored, the real-time data of the variables are stored into the time sequence database, and the expired data is automatically cleared after the expiration according to the set effective time length of data storage; if the variable is judged not to be stored, the variable can only use the real-time data function;
s4, equipment management based on object model: and uniformly managing equipment variable information, equipment states and data in the equipment synchronized to the object model management service cluster, checking and reversely controlling and issuing, and uploading the equipment states to the middleware of the Internet of things through a protocol according to data acquired by actual equipment.
5. The method for implementing the internet of things middleware-based industrial object model according to claim 4, wherein in the step S1, the identity information is used for defining the name, number, source, type and extensible information of the object model; the attribute information is used for defining specific information and states of the equipment, and the operation types are divided into read-only types, write-only types and read-write types; the event information is used for defining information actively reported to the cloud end when the equipment runs, and comprises information needing to be sensed and processed by the outside, alarm and fault; the service information is used for defining an instruction or a method which can be called by the equipment from the outside, and complex business logic is realized.
6. The method for implementing the internet of things middleware-based industrial object model according to claim 5, wherein the service sources comprise: the system comprises an industrial Internet of things gateway, MQTT direct connection equipment and a soft gateway.
7. The method for implementing the internet of things middleware-based industrial object model according to claim 4, wherein the protocol in the step S4 includes: one or more of http, mqtt, OPC and Modbus.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210411759.3A CN114510219B (en) | 2022-04-19 | 2022-04-19 | Industrial object model based on middleware of Internet of things and implementation method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210411759.3A CN114510219B (en) | 2022-04-19 | 2022-04-19 | Industrial object model based on middleware of Internet of things and implementation method thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114510219A CN114510219A (en) | 2022-05-17 |
| CN114510219B true CN114510219B (en) | 2022-07-19 |
Family
ID=81555486
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210411759.3A Active CN114510219B (en) | 2022-04-19 | 2022-04-19 | Industrial object model based on middleware of Internet of things and implementation method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114510219B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116527446B (en) * | 2023-02-01 | 2023-09-08 | 合沃物联技术（南京）有限公司 | Edge rule engine method based on industrial Internet of things gateway |
| CN116320078B (en) * | 2023-05-24 | 2023-08-11 | 深圳市亲邻科技有限公司 | Internet of things converged communication system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110505312B (en) * | 2019-09-09 | 2022-05-10 | 合肥移瑞通信技术有限公司 | Internet of things platform management system capable of being deployed at high end |
| CN111641583B (en) * | 2020-04-07 | 2021-09-03 | 北京邮电大学 | Internet of things resource access system and resource access method |
| CN113805867B (en) * | 2021-08-24 | 2024-03-19 | 中通服咨询设计研究院有限公司 | Internet of things platform based on visual static script engine |
-
2022
- 2022-04-19 CN CN202210411759.3A patent/CN114510219B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN114510219A (en) | 2022-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114510219B (en) | Industrial object model based on middleware of Internet of things and implementation method thereof | |
| CN108809701A (en) | A kind of data center's wisdom data platform and its implementation | |
| CN101242549A (en) | Neutral network construction method for communication network alarm association | |
| CN102291247A (en) | Alarm association diagram generation method and device and association alarm determination method and device | |
| CN114253228B (en) | Industrial equipment object modeling method and device based on digital twin | |
| CN109240876A (en) | Example monitoring method, computer readable storage medium and terminal device | |
| CN104570980A (en) | B/S-architecture-based cross-platform remote monitoring system for numerical control machining production line | |
| CN107179977B (en) | Database Full-automatic monitoring system based on mpm models | |
| CN110765077A (en) | Method and system for uniformly managing AI model based on distributed file system | |
| CN111782672B (en) | Multi-field data management method and related device | |
| CN116340413A (en) | Internet of things edge data acquisition and storage method | |
| CN115660620A (en) | Personnel DB library management method and device based on RPA and storage medium | |
| CN113792008A (en) | Method and device for acquiring network topology structure, electronic equipment and storage medium | |
| CN113434123A (en) | Service processing method and device and electronic equipment | |
| CN111736568A (en) | Method and system for rapidly diagnosing faults of real-time database | |
| CN113742393B (en) | Time sequence data processing system suitable for Internet application | |
| CN113783862B (en) | Method and device for checking data in edge cloud cooperation process | |
| CN115756395A (en) | Multi-dimensional object data statistical method based on annotation configuration | |
| CN112953754B (en) | Configuration method and device of differentiated service, electronic equipment and storage medium | |
| CN114626228A (en) | Digital twin model construction method | |
| CN112669015B (en) | Power dispatching micro-service construction system and method | |
| CN110457402A (en) | A kind of data reconstruction method and device based on hadoop frame model | |
| CN111459965B (en) | Information monitoring system for edge calculation | |
| CN117215791A (en) | Task grade determining method, device, equipment and medium | |
| CN117453829A (en) | Knowledge graph data synchronization method and computer |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |