CN112637076B - Industrial Internet of things data transmission Worker service implementation method and device - Google Patents
Industrial Internet of things data transmission Worker service implementation method and device Download PDFInfo
- Publication number
- CN112637076B CN112637076B CN202011517436.XA CN202011517436A CN112637076B CN 112637076 B CN112637076 B CN 112637076B CN 202011517436 A CN202011517436 A CN 202011517436A CN 112637076 B CN112637076 B CN 112637076B
- Authority
- CN
- China
- Prior art keywords
- data
- routing information
- rule
- rule engine
- engine
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- 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/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses a method and a device for realizing an industrial Internet of things data transmission Worker service, wherein the method comprises the steps of acquiring routing information from a DC system by utilizing a routing information request interface when the Worker service is started; matching the Controller service according to the routing information, and interacting with the matched Controller service through the Helix service; acquiring and updating a rule engine from a DC system by using a rule engine request interface at preset time intervals; ConsumerRecord data was batch processed using the IMessageTransformer interface. According to the method and the device, the route matching Controller is obtained according to the configuration file parameters, the data are obtained through the route when the data are processed, the device data type is identified according to the rule engine, and the problem that the industrial device data are uniformly sent through the gateway to be mixed is solved.
Description
Technical Field
The invention belongs to the technical field of industrial Internet of things data transmission, and relates to a method and a device for realizing an industrial Internet of things data transmission Worker service.
Background
In the current ecology of the industrial equipment data system, the equipment data is uploaded to an external Kafka cluster in real time by the acquisition gateway. However, in the process of acquiring data uploaded by a gateway, different data structures of the same equipment data are mixed with each other, equipment state identifications of different manufacturers are the same, the data are transmitted by a plurality of pieces of equipment, the types of the equipment are different, and the equipment needs to be created, so that subsequent data cleaning is complex, new development tasks are required for processing the data when new equipment data are added, and operation and maintenance workload is increased when a Kafka cluster needs to create new pieces of Topic.
Disclosure of Invention
In order to solve the technical problems of the related technology, the application provides a method and a device for realizing the Worker service of data transmission of the industrial Internet of things, and the technical scheme is as follows:
in a first aspect, the application provides a method for implementing an industrial internet of things data transmission Worker service, and the method includes:
when the Worker service is started, acquiring routing information from a DC system by utilizing a developed routing information request interface, wherein the routing information comprises Kafka cluster routing information of a consumer and Kafka cluster routing information of a producer;
matching a Controller service according to the routing information, and interacting with the matched Controller service through a Helix service;
obtaining and updating a rules engine from the DC system at predetermined time intervals using a developed rules engine request interface, the rules engine comprising: srcotipic, DestTopic, rule conditions, and rule elements;
the developed RuleMessageTransformer class is used for realizing an IMessageTransformer interface, and ConsumerRecord data is processed in a data batch processing processList method by using the IMessageTransformer interface.
Optionally, the obtaining the routing information from the DC system by using the developed routing information request interface includes:
and calling the routing information request interface through prestored configuration file parameters to access the DC system, and acquiring routing information from the DC system.
Optionally, the acquiring and updating a rule engine from the DC system by using a developed rule engine request interface at predetermined time intervals includes:
creating an ExecutorService thread pool in a Worker service WorkerInstance class;
acquiring all rule engine Map sets in the current routing information from the DC system at preset time intervals by using the ExecutionService thread pool;
and the reference of the rule engine Map set points to the rule engine Map set in the developed RuleMessageTransformer class, so that the data rule engine is updated and the rule engine is updated.
Optionally, the processing ConsumerRecord data in the batch processing processList method by using the IMessageTransformer interface includes:
and matching a rule engine corresponding to the ConsumerRecord data from the rule engine in a processList method by utilizing an IMessageTransformer interface, processing the ConsumerRecord data by utilizing a matched rule element in the rule engine, and finishing the transmission of data batch multiple data sources in a ProducerThread class.
Optionally, the matching, from the rule engines, a rule engine corresponding to the ConsumerRecord data includes:
finding out a corresponding rule engine Map set according to SrcTopic information of the Consumer record data;
traversing the rule engine Map set, converting the rule conditions of the rule engine into a regular expression, and matching the regular expression with Value information of the ConsumerRecord data.
Optionally, the processing the ConsumerRecord data by using the matched rule element in the rule engine includes:
cleansing and/or dictionary mapping said ConsumerRecord data with matching rule elements in said rules engine.
Optionally, after the processing the ConsumerRecord data with the matched rule elements in the rule engine, the method further includes:
packaging the processed Consumer record data and the corresponding DestTopic in the rule engine into a Producerrecord;
and writing the production record ProducerRecord into a ProducerRecord set.
Optionally, the method further comprises:
developing a producer Thread ProducerThread class, inheriting the Thread class, and calling a RuleMessageTransformant class processList method in a run method to obtain a ProducerRecord set.
Optionally, the method further comprises:
and traversing the ProducerRecord set, and sending the DestTopic of each rule engine to the Topic of the corresponding producer Kafka cluster.
Optionally, the customer Kafka cluster routing information includes: the Kafka cluster address of the consumer, the group of the consumer and the Zookeeper cluster address of the Kafka cluster of the consumer;
the producer Kafka cluster routing information includes a producer Kafka cluster address.
In a second aspect, the present application further provides an industrial internet of things data transmission Worker service implementation device, the device includes:
the system comprises a routing information acquisition module, a route information acquisition module and a route information acquisition module, wherein the routing information acquisition module is used for acquiring routing information from a DC system by utilizing a developed routing information request interface when the Worker service is started, and the routing information comprises Kafka cluster routing information of a consumer and Kafka cluster routing information of a producer;
the matching module is used for matching the Controller service according to the routing information and interacting with the matched Controller service through Helix service;
a rule engine update module for acquiring and updating a rule engine from the DC system at predetermined time intervals using a developed rule engine request interface, the rule engine comprising: srcotipic, DestTopic, rule conditions, and rule elements;
and the data processing module is used for realizing an IMessageTransformer interface by utilizing the developed RuleMessageTransformer class and processing ConsumerRecord data in the data batch processing processList method by utilizing the IMessageTransformer interface.
Through above-mentioned technical scheme, this application can realize following beneficial effect at least:
the Worker acquires the route matching Controller according to the configuration file parameters, acquires data through the route when processing the data, identifies the device data type according to the rule engine, and solves the problem that industrial device data uniformly sends data through the gateway to be mixed.
In addition, the Worker consumes the data and completes the cleaning operation of the equipment data at the same time, thereby solving the problem of real-time cleaning of the industrial equipment data; and a new rule engine is only required to be added when a new equipment data source is added, a new task is not required to be developed, and the development cost and the operation and maintenance cost are reduced.
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 invention as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
Fig. 1 is a flowchart of an implementation method of an industrial internet of things data transmission Worker service provided in an embodiment of the present application;
fig. 2 is a flowchart of an implementation method of an industrial internet of things data transmission Worker service provided in another embodiment of the present application;
fig. 3 is a schematic structural diagram of an industrial internet of things data transmission Worker service implementation device provided in an embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
Fig. 1 is a flowchart of an industrial internet of things data transmission Worker service implementation method provided in an embodiment of the present application, where the industrial internet of things data transmission Worker service implementation method is applied to a Worker service, and the method includes the following steps:
and a routing information request interface is developed in the Worker service in advance, and when the Worker service is started, the developed routing information request interface is utilized to acquire routing information from the DC system.
The routing information mentioned here includes the consumer Kafka cluster routing information and the producer Kafka cluster routing information, and in general, the consumer Kafka cluster routing information may include a consumer Kafka cluster address, a consumer group, and a Zookeeper cluster address where the consumer Kafka cluster is located; the producer Kafka cluster routing information may include a producer Kafka cluster address.
In one possible implementation, in performing step 101, the routing information request interface may be invoked via pre-stored profile parameters to access the DC system, and obtain routing information from the DC system.
generally, the DC system may store routing information and a rule engine in advance, and provide a routing rule service and a rule engine service for the Worker.
Firstly, creating an ExecutorService thread pool in a Worker service WorkerInstance class; then, acquiring all rule engine Map sets in the current routing information from the DC system at preset time intervals by using the ExecutionService thread pool; and finally, the reference of the rule engine Map set points to the rule engine Map set in the developed RuleMessageTransformer class, so that the data rule engine is updated and the rule engine is updated.
The predetermined time interval may be set according to an actual situation, for example, may be set to 30s, 25s, or 35s, and the specific value of the predetermined time interval is not limited in this application.
The rules engine as referred to herein may include: srcotipic, DestTopic, rule conditions, and rule elements.
And step 104, realizing an IMessageTransformer interface by using the developed RuleMessageTransformer class, and processing ConsumerRecord data in a data batch processing processList method by using the IMessageTransformer interface.
And matching a rule engine corresponding to the ConsumerRecord data from the rule engine in a processList method by utilizing an IMessageTransformer interface, processing the ConsumerRecord data by utilizing rule elements in the matched rule engine, and completing data batch multi-data source transmission in a ProducerThread class.
When a rule engine corresponding to the ConsumerRecord data is matched from the rule engines, a corresponding rule engine Map set can be found according to srcotipic information of the ConsumerRecord data; and traversing the rule engine Map set, converting the rule conditions of the rule engine into a regular expression, and matching the regular expression with Value information of the ConsumerRecord data.
Optionally, when processing the ConsumerRecord data by using the matched rule elements in the rule engine, the ConsumerRecord data may be cleaned and/or dictionary mapped by using the matched rule elements in the rule engine.
In one possible implementation, a producer Thread ProducerThread class is developed in the Worker and inherits the Thread class, and a RuleMessageTransformant class processList method is called in the run method to obtain a ProducerRecord set.
Further, after processing the ConsumerRecord data by using the matched rule elements in the rule engine, the method further includes: packaging the processed Consumer record data and the corresponding DestTopic in the rule engine into a Producerrecord; and writing the production record ProducerRecord into a ProducerRecord set.
Further, the ProducerRecord set is traversed, and the DestTopic of each rule engine is sent to the Topic of the corresponding producer Kafka cluster.
To sum up, the method for realizing the data transmission Worker service of the industrial internet of things obtains the route matching Controller according to the configuration file parameters in the Worker, obtains data through the route when processing the data, identifies the device data type according to the rule engine, and solves the problem that the industrial device data uniformly sends data mixing through the gateway.
In addition, the Worker consumes the data and completes the cleaning operation of the equipment data at the same time, thereby solving the problem of real-time cleaning of the industrial equipment data; and a new rule engine is only required to be added when a new equipment data source is added, a new task is not required to be developed, and the development cost and the operation and maintenance cost are reduced.
Fig. 2 is a flowchart of an industrial internet of things data transmission Worker service implementation method provided in another embodiment of the present application, where the industrial internet of things data transmission Worker service implementation method is applied to a Worker service, and the method includes the following steps:
here, refer to the Worker start-up.
generally speaking, a DC system may provide routing rule services and rule engine services. And after the Worker is started, calling a routing rule service of the DC system to acquire a routing rule, and matching a Controller according to the routing information.
For a detailed explanation, refer to step 101 and step 102, which are not described herein.
the implementation of step 203 and step 204 can be seen in step 103.
and step 207, writing the target source Kafka cluster data.
Steps 205-207 can be seen in the explanation of step 104.
To sum up, the method for realizing the data transmission Worker service of the industrial internet of things obtains the route matching Controller according to the configuration file parameters in the Worker, obtains data through the route when processing the data, identifies the device data type according to the rule engine, and solves the problem that the industrial device data uniformly sends data mixing through the gateway.
In addition, the Worker consumes the data and completes the cleaning operation of the equipment data at the same time, thereby solving the problem of real-time cleaning of the industrial equipment data; and a new rule engine is only required to be added when a new equipment data source is added, a new task is not required to be developed, and the development cost and the operation and maintenance cost are reduced.
In the following, for the embodiments of the device for implementing the data transmission Worker service of the industrial Internet of things provided by the application, since the device embodiments correspond to the method embodiments, the following related technical features of the device embodiments may refer to the explanations of the embodiments of the method for implementing the data transmission Worker service of the industrial Internet of things, and are not described in detail here.
Fig. 3 is a schematic structural diagram of an industrial internet of things data transmission Worker service implementation device provided in an embodiment of the present application, where the industrial internet of things data transmission Worker service implementation device may include: a routing information acquisition module 310, a matching module 320, a rule engine update module 330, and a data processing module 340.
The routing information obtaining module 310 may be configured to obtain routing information from the DC system using the developed routing information request interface when the Worker service is started, where the routing information includes customer Kafka cluster routing information and producer Kafka cluster routing information.
In one possible implementation, the routing information obtaining module 310 may be further configured to call the routing information request interface to access the DC system through a pre-stored configuration file parameter, so as to obtain routing information from the DC system.
Optionally, the customer Kafka cluster routing information may include: the Kafka cluster address of the consumer, the group of the consumer and the Zookeeper cluster address of the Kafka cluster of the consumer; the producer Kafka cluster routing information may include a producer Kafka cluster address.
The matching module 320 may be configured to match a Controller service according to the routing information, and interact with the matched Controller service through a help service.
The rules engine update module 330 may be configured to obtain and update rules engines from the DC system at predetermined time intervals using a developed rules engine request interface, the rules engines including: srcotipic, DestTopic, rule conditions, and rule elements.
In one possible implementation, the rule engine update module 330 may also be configured to create an ExecutorService thread pool in the Worker service WorkerInstance class; acquiring all rule engine Map sets in the current routing information from the DC system at preset time intervals by using the ExecutionService thread pool; and the reference of the rule engine Map set points to the rule engine Map set in the developed RuleMessageTransformer class, so that the data rule engine is updated and the rule engine is updated.
The data processing module 340 may be configured to implement an IMessageTransformer interface using the developed RuleMessageTransformer class, and process ConsumerRecord data in the data batch processing processList method using the IMessageTransformer interface.
In a possible implementation, the data processing module 340 may further match, in a processList method, a rule engine corresponding to the ConsumerRecord data from the rule engine by using an imessagefransformer interface, process the ConsumerRecord data by using a rule element in the matched rule engine, and complete data batch multiple data source transmission in a producer thread class.
Further, the data processing module 340 may also find a corresponding rule engine Map set according to srcotipic information of the ConsumerRecord data; traversing the rule engine Map set, converting the rule conditions of the rule engine into a regular expression, and matching the regular expression with Value information of the ConsumerRecord data.
Further, the data processing module 340 may also perform cleansing and/or dictionary mapping on the ConsumerRecord data using the matched rule elements in the rule engine.
Optionally, the device for realizing the data transmission Worker service of the industrial internet of things provided by the application may further include a writing device, and may be configured to implement the following steps:
packaging the processed Consumer record data and the corresponding DestTopic in the rule engine into a Producerrecord;
and writing the production record ProducerRecord into a ProducerRecord set.
Optionally, the device for implementing the data transmission Worker service of the industrial internet of things provided by the application may further include a set obtaining device, and may be configured to implement the following steps:
developing a producer Thread ProducerThread class, inheriting the Thread class, and calling a RuleMessageTransformant class processList method in a run method to obtain a ProducerRecord set.
Optionally, the device for realizing the data transmission Worker service of the industrial internet of things provided by the application may further include a sending device, and may be configured to implement the following steps:
and traversing the ProducerRecord set, and sending the DestTopic of each rule engine to the Topic of the corresponding producer Kafka cluster.
To sum up, the device for realizing the data transmission Worker service of the industrial internet of things obtains the route matching Controller according to the configuration file parameters in the Worker, obtains data through the route when processing the data and identifies the data type of the equipment according to the rule engine, and solves the problem that the industrial equipment data uniformly sends the data mixing through the gateway.
In addition, in the Worker, the cleaning operation of the equipment data is completed while the data is consumed, so that the problem of real-time cleaning of the industrial equipment data is solved; and a new rule engine is only required to be added when a new equipment data source is added, a new task is not required to be developed, and the development cost and the operation and maintenance cost are reduced.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
It will be understood that the invention is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the invention is limited only by the appended claims.
Claims (9)
1. A method for realizing data transmission Worker service of an industrial Internet of things is characterized by comprising the following steps:
when the Worker service is started, acquiring routing information from a DC system by utilizing a developed routing information request interface, wherein the routing information comprises Kafka cluster routing information of a consumer and Kafka cluster routing information of a producer;
matching a Controller service according to the routing information, and interacting with the matched Controller service through a Helix service;
obtaining and updating a rules engine from the DC system at predetermined time intervals using a developed rules engine request interface, the rules engine comprising: srcotipic, DestTopic, rule conditions, and rule elements;
realizing an IMessageTransformer interface by utilizing developed RuleMessageTransformer classes, and processing ConsumerRecord data in a data batch processing processList method by utilizing the IMessageTransformer interface;
the processing of ConsumerRecord data in a batch processing processList method by using an IMessageTransformer interface comprises the following steps:
matching a rule engine corresponding to the Consumer record data from the rule engine by using an IMessageTransformer interface in a processList method, processing the Consumer record data by using a rule element in the matched rule engine, and completing data batch multi-data source transmission in a ProducerThread class;
processing the ConsumerRecord data by using the matched rule elements in the rule engine, wherein the processing comprises the following steps:
and cleaning and/or dictionary mapping the ConsumerRecord data by utilizing the matched rule elements in the rule engine.
2. The method of claim 1, wherein obtaining routing information from the DC system using the developed routing information request interface comprises:
and calling the routing information request interface through prestored configuration file parameters to access the DC system, and acquiring routing information from the DC system.
3. The method of claim 1, wherein obtaining and updating a rules engine from the DC system at predetermined time intervals using a developed rules engine request interface comprises:
creating an ExecutorService thread pool in a Worker service WorkerInstance class;
acquiring all rule engine Map sets in the current routing information from the DC system at preset time intervals by using the ExecutionService thread pool;
and the reference of the rule engine Map set points to the rule engine Map set in the developed RuleMessageTransformer class, so that the data rule engine is updated and the rule engine is updated.
4. The method of claim 1, wherein said matching from said rule engines a rule engine corresponding to said ConsumerRecord data comprises:
finding out a corresponding rule engine Map set according to SrcTopic information of the Consumer record data;
traversing the rule engine Map set, converting the rule conditions of the rule engine into a regular expression, and matching the regular expression with Value information of the ConsumerRecord data.
5. The method of claim 1, wherein after said processing said ConsumerRecord data with matched rule elements in said rule engine, said method further comprises:
packaging the processed Consumer record data and the corresponding DestTopic in the rule engine into a Producerrecord;
and writing the production record ProducerRecord into a ProducerRecord set.
6. The method of claim 5, further comprising:
developing a producer Thread ProducerThread class, inheriting the Thread class, and calling a RuleMessageTransformant class processList method in a run method to obtain a ProducerRecord set.
7. The method of claim 5, further comprising:
and traversing the ProducerRecord set, and sending the DestTopic of each rule engine to the Topic of the corresponding producer Kafka cluster.
8. The method of any of claims 1 to 7, wherein the consumer Kafka cluster routing information comprises: the Kafka cluster address of the consumer, the group of the consumer and the Zookeeper cluster address of the Kafka cluster of the consumer;
the producer Kafka cluster routing information includes a producer Kafka cluster address.
9. The utility model provides an industry thing networking data transmission Worker service realizes device which characterized in that, the device includes:
the system comprises a routing information acquisition module, a route information acquisition module and a route information acquisition module, wherein the routing information acquisition module is used for acquiring routing information from a DC system by utilizing a developed routing information request interface when the Worker service is started, and the routing information comprises Kafka cluster routing information of a consumer and Kafka cluster routing information of a producer;
the matching module is used for matching the Controller service according to the routing information and interacting with the matched Controller service through Helix service;
a rules engine update module for obtaining and updating rules engines from the DC system at predetermined time intervals using a developed rules engine request interface, the rules engine comprising: srcotipic, DestTopic, rule conditions, and rule elements;
the data processing module is used for realizing an IMessageTransformer interface by utilizing developed RuleMessageTransformer classes and processing ConsumerRecord data in a data batch processing processList method by utilizing the IMessageTransformer interface;
the processing of ConsumerRecord data in a batch processing processList method by using an IMessageTransformer interface comprises the following steps:
matching a rule engine corresponding to the Consumer record data from the rule engine by using an IMessageTransformer interface in a processList method, processing the Consumer record data by using a rule element in the matched rule engine, and completing data batch multi-data source transmission in a ProducerThread class;
processing the ConsumerRecord data by using the matched rule elements in the rule engine, wherein the processing comprises the following steps:
and cleaning and/or dictionary mapping the ConsumerRecord data by utilizing the matched rule elements in the rule engine.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011517436.XA CN112637076B (en) | 2020-12-21 | 2020-12-21 | Industrial Internet of things data transmission Worker service implementation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011517436.XA CN112637076B (en) | 2020-12-21 | 2020-12-21 | Industrial Internet of things data transmission Worker service implementation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112637076A CN112637076A (en) | 2021-04-09 |
| CN112637076B true CN112637076B (en) | 2022-08-02 |
Family
ID=75320302
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011517436.XA Active CN112637076B (en) | 2020-12-21 | 2020-12-21 | Industrial Internet of things data transmission Worker service implementation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112637076B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107908690A (en) * | 2017-11-01 | 2018-04-13 | 南京欣网互联网络科技有限公司 | A kind of data processing method based on big data OA operation analysis |
| EP3340571A1 (en) * | 2016-12-20 | 2018-06-27 | ABB Schweiz AG | Gateway for transmitting data from a source system to a destination system, with rule-based forwarding and further processing of data, and method |
| CN109617796A (en) * | 2018-11-15 | 2019-04-12 | 江苏东洲物联科技有限公司 | A kind of edge calculations gateway of rule-based engine |
| CN110677276A (en) * | 2019-09-09 | 2020-01-10 | 杭州玖欣物联科技有限公司 | System for realizing multi-user hot deployment supported by industrial internet data processing |
-
2020
- 2020-12-21 CN CN202011517436.XA patent/CN112637076B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3340571A1 (en) * | 2016-12-20 | 2018-06-27 | ABB Schweiz AG | Gateway for transmitting data from a source system to a destination system, with rule-based forwarding and further processing of data, and method |
| CN107908690A (en) * | 2017-11-01 | 2018-04-13 | 南京欣网互联网络科技有限公司 | A kind of data processing method based on big data OA operation analysis |
| CN109617796A (en) * | 2018-11-15 | 2019-04-12 | 江苏东洲物联科技有限公司 | A kind of edge calculations gateway of rule-based engine |
| CN110677276A (en) * | 2019-09-09 | 2020-01-10 | 杭州玖欣物联科技有限公司 | System for realizing multi-user hot deployment supported by industrial internet data processing |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112637076A (en) | 2021-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107407918B (en) | Extending programmable logic controllers with app | |
| US7869887B2 (en) | Discoverable services | |
| US20210406037A1 (en) | Field device configuration tool | |
| CN104850491A (en) | Software test method, equipment and system | |
| CN110768914A (en) | Decentralized Internet of things gateway system based on semantic scene instance migration | |
| CN111178837A (en) | Intelligent manufacturing information system based on micro-service architecture | |
| CN109782720A (en) | The method that control is directly realized by by process logic topological diagram | |
| CN112637076B (en) | Industrial Internet of things data transmission Worker service implementation method and device | |
| CN111651365A (en) | Automatic interface testing method and device | |
| CN111597676B (en) | System and method for checking system requirements of information physical system | |
| CN113032093A (en) | Distributed computing method, device and platform | |
| Guo et al. | The application of OPC DA in factory data acquisition | |
| CN110298630A (en) | A kind of workflow engine | |
| JP2005044111A (en) | Field bus system | |
| CN101500001A (en) | Network service system and implementing method | |
| CN114726911B (en) | Routing parameter transfer method for distributed industrial robot online service arrangement | |
| WO2021197754A1 (en) | Generating a multi-hierarchical representation of a technical arrangement | |
| CN102662685A (en) | Method and device for installing driver of terminal equipment | |
| CN114418456B (en) | Machine learning progress control method based on working conditions and related device | |
| Raileanu et al. | Towards an ontology for distributed manufacturing control | |
| CN112463344B (en) | Data analysis method and device | |
| CN116795434B (en) | Pipelined task processing method and device, electronic equipment and storage medium | |
| CN109388415A (en) | A kind of application automation updating device, system and method | |
| CN116141342B (en) | Information synchronization and task cooperation method and device of distributed robot and robot | |
| CN113157352B (en) | Programmable front-end controller implementation method, programmable front-end controller implementation device, programmable front-end controller implementation equipment and programmable front-end controller implementation medium |
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 |