CN113987047B - OPC-UA protocol-based automatic data acquisition method - Google Patents
OPC-UA protocol-based automatic data acquisition method Download PDFInfo
- Publication number
- CN113987047B CN113987047B CN202111299303.4A CN202111299303A CN113987047B CN 113987047 B CN113987047 B CN 113987047B CN 202111299303 A CN202111299303 A CN 202111299303A CN 113987047 B CN113987047 B CN 113987047B
- Authority
- CN
- China
- Prior art keywords
- tag
- real
- time database
- opc
- queue
- 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
- 238000000034 method Methods 0.000 title claims abstract description 26
- 230000008569 process Effects 0.000 claims abstract description 10
- 238000013480 data collection Methods 0.000 claims abstract 4
- 230000006870 function Effects 0.000 claims description 20
- 230000004048 modification Effects 0.000 claims description 18
- 238000012986 modification Methods 0.000 claims description 18
- 238000012217 deletion Methods 0.000 claims description 15
- 230000037430 deletion Effects 0.000 claims description 15
- 238000012545 processing Methods 0.000 claims description 12
- 238000004806 packaging method and process Methods 0.000 claims description 7
- 230000001360 synchronised effect Effects 0.000 claims description 7
- 238000001914 filtration Methods 0.000 claims description 4
- 238000004891 communication Methods 0.000 abstract description 14
- 238000005259 measurement Methods 0.000 abstract 1
- 230000008901 benefit Effects 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- 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/25—Integrating or interfacing systems involving database management systems
-
- 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/2228—Indexing structures
- G06F16/2246—Trees, e.g. B+trees
-
- 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/2228—Indexing structures
- G06F16/2255—Hash tables
-
- 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/23—Updating
-
- 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses an OPC-UA communication protocol-based automatic data acquisition method, which mainly comprises the following four parts: newly added points, namely, newly added points are synchronously created in a real-time database, and data are automatically collected; the measuring points are modified, namely new adding measuring points are synchronously created in a real-time database, and automatic data collection is started; deleting a measuring point, namely stopping subscription of the measuring point, and simultaneously writing a log record; synchronizing the measuring point data, namely collecting the effective measuring point data and writing the effective measuring point data into a real-time database; the method provided by the invention can synchronize the measurement point information and the data of the local device to the real-time database, can completely replace manual operation, improves the working efficiency, reduces the error rate of the manual operation, greatly simplifies the complexity of data acquisition, can effectively save time in the field implementation process, and provides convenience for staff.
Description
Technical Field
The invention relates to an OPC-UA protocol, which belongs to the field of network data transmission, in particular to an OPC-UA protocol-based automatic data acquisition method, which is used for automatically synchronizing information and data of measuring points in a power plant to a real-time database.
Background
Real-time databases are commonly used by power plants in daily operations to store the relevant data generated, but the tags of the databases are usually manually added to the databases one by one, or form files are manually filled out and then imported into the real-time databases. Because the data is added by manual operation, the time is additionally spent to finish the work, and the data errors and omission caused by human factors can also influence the accuracy of data storage.
In 2006, the OPC foundation introduced OPC-UA (Unified Architecture) communication specifications, which are inheritance and upgrade of OPC-DA, to make up for the shortages of OPC technology in terms of cross-platform, security and modeling capability. The OPC-UA protocol has 7 characteristics: (1) access uniformity: the user can obtain all the information only by accessing once. (2) service oriented architecture: the application is independent of the platform, operating system, programming language. (3) high performance communication: the communication stack is used for coding, encrypting and transmitting data, single-port communication is adopted, and communication is faster. (4) higher security: the security is ensured by using asymmetric encryption and an X.509 certificate, and the identity authentication mechanism of the security can effectively defend malicious attacks in a network and ensure safe and reliable communication. (5) reliability and redundancy: the redundancy check technology is used, and the automatic error checking and correcting capability is provided. (6) C/S and Pub/Sub implementation mechanism: OPC-UA provides two different implementation mechanisms: one is a client/server model (C/S) based primarily on TCP, and one is a publisher/subscriber model (Pub/Sub) based primarily on UDP. Different implementation mechanisms apply to unused scenarios. (7) object-oriented modeling: OPC-UA has strong modeling capability, and can build flexible information model by using object-oriented ideas to perform information modeling.
Disclosure of Invention
In order to solve the existing problems in the data acquisition process, and combine the advantages of the OPC-UA protocol, the invention provides an automatic data acquisition method based on the OPC-UA protocol, which can realize the following purposes that when the label information of a server side changes, the label information is automatically compared with preset label filtering conditions, and for the measuring points meeting the conditions, the measuring points corresponding to a real-time database can be automatically added, modified or deleted. Compared with the prior art, the method has the advantages of full-automatic synchronous measuring point information, safety, reliability, high efficiency and the like.
The invention is realized by the following technical scheme:
an OPC-UA protocol-based automatic data acquisition method comprises the following specific steps:
step 1: acquiring the connection state of the equipment and the real-time database, if the equipment is not connected for data connection, the connection is successful in the step 2, and the connection is failed in the step 11;
step 2: acquiring existing point table information in a real-time database, generating an existing tag table corresponding to the database, and performing step 3;
step 3: acquiring the connection state of the equipment and the OPC-UA server, if the equipment is not connected for data connection, the connection is successful in the step 4, and the connection failure is in the step 11;
step 4: acquiring label information from an OPC-UA server, performing filtering operation, generating an effective label table, and performing step 5;
step 5: comparing the existing tag list with the effective tag list, adding the tags needing to be added, modified and deleted into the corresponding tag processing queues, and performing step 6;
step 6: judging whether the newly added queue is empty, and if so, performing the next operation; otherwise, calling a tag operation function of the real-time database, setting an operation instruction to be newly added, and performing newly added tag operation; if the operation is successful, updating the existing tag table, and performing step 7;
step 7: judging whether the modification queue is empty or not, and if so, performing the next operation; otherwise, calling a tag operation function of the real-time database, setting an operation instruction as modification, and carrying out tag modification operation; if the operation is successful, updating the existing tag table, and returning to the step 8;
step 8: judging whether the deleting queue is empty or not, and if so, performing the next operation; otherwise, calling a tag operation function of the real-time database, setting an operation instruction to be deleted, and performing tag deletion operation; if the operation is successful, updating the existing tag table, and returning to the step 9;
step 9: transmitting an instruction for acquiring data to an OPC-UA server, and acquiring data corresponding to the effective label from the OPC-UA server in a synchronous mode or a subscription mode; if the error is captured, step 11 is performed, otherwise step 10 is invoked;
step 10: calling a snapshot writing function of the real-time database, and synchronizing the collected real-time data into the real-time database; if the data are acquired in a synchronous mode, executing the step 9; if the error is captured, step 11 is performed;
step 11: and acquiring the error information, calling a corresponding processing scheme to process, and writing the error which is not solved into the log to record.
The detailed process of adding the tag to the real-time database in the step 6 is as follows:
step 6.1: judging whether the newly added tag queue is empty, if so, performing step 7, otherwise, performing step 6.2;
step 6.2: traversing the newly added queue, packaging all the corresponding structures of the newly added tags, calling tag operation functions of the real-time database, and setting the operation instructions as newly added tags; if the new addition is successful, the new addition queue is emptied and the step 7 is carried out, otherwise, the step 6.3 is carried out;
step 6.3: counting error codes and writing the error codes into a log; when the number of errors exceeds a set value, alarm sending operation is carried out; if the set value is not exceeded, performing error processing.
The detailed process of modifying the tag by the real-time database in the step 7 is as follows:
step 7.1: judging whether the modified tag queue is empty, if so, performing step 8, otherwise, performing step 7.2;
step 7.2: traversing the update queue, packaging all the structure bodies corresponding to the modification tags, calling tag operation functions of the real-time database, and setting the operation instructions as modification; if the modification is successful, the modification queue is emptied and the step 8 is carried out, otherwise, the step 7.3 is carried out;
step 7.3: counting error codes and writing the error codes into a log; when the number of errors exceeds a set value, alarm sending operation is carried out; if the set value is not exceeded, performing error processing.
The detailed process of deleting the tag from the real-time database in the step 8 is as follows:
step 8.1: judging whether the tag deleting queue is empty, if so, performing step 9, otherwise, performing step 8.2;
step 8.2: traversing the deletion queue, packaging all corresponding structures of the deletion tags, calling tag operation functions of the real-time database, and setting operation instructions as deletion; if the deletion is successful, the deletion queue is emptied and the step 9 is carried out, otherwise, the step 8.3 is carried out;
step 8.3: counting error codes and writing the error codes into a log; when the number of errors exceeds a set value, alarm sending operation is carried out; if the set value is not exceeded, performing error processing.
The invention has at least the following beneficial technical effects:
1. the method provided by the invention benefits from the advantages of OPC-UA protocol, and has high efficiency, safety, reliability and redundancy. The field test can completely meet the data acquisition and label synchronization functions of 7 tens of thousands of label seconds.
2. The invention can effectively improve the working efficiency, and can realize automatic data acquisition and storage by only one configuration, namely without manual intervention.
Drawings
FIG. 1 is a communication schematic diagram of an OPC-UA server and client of the present invention;
fig. 2 is a flow chart of the operation of the present invention.
Detailed Description
Communication parsing of OPC-UA protocol and specific description of key technology of the system will be described in detail with reference to the accompanying drawings. The specific embodiments described herein are to be considered in an illustrative rather than a restrictive sense. In addition, it should be noted that, in the drawings, only some, but not all of the structures related to the present invention are shown for convenience of description.
The communication principle of OPC-UA server and client is shown in fig. 1, comprising OPC-UA communication stack, OPC-UA server and client interface, and OPC-UA server and client application 5 parts. As can be seen from fig. 1, there are two interactive modes, in which the subscription mode is that the client sends a publishing request through the client interface, the communication stack converts the publishing request into a publishing message, and then sends the publishing message to the server communication stack through the bottom communication entity, the server interface sends the publishing message to the client, and once the node item to be monitored is specified to change, the subscribing sends a notification message to the client. The invention adopts the subscription mode of OPC-UA to obtain data as main and the interactive mode as auxiliary to obtain data. In practice, there is a phenomenon of time waste when acquiring a node. In order to better improve the OPC-UA efficiency, the node storage mode of the Open62541-v0.3 Open source library is modified, the linked list data structure is modified into a red black tree data structure, and the speed of acquiring the nodes is greatly improved.
The operation flow of the invention is shown in fig. 2, and comprises the following steps:
step 1: acquiring the connection state of the equipment and the real-time database, if the equipment is not connected for data connection, the connection is successful in the step 2, and the connection is failed in the step 11;
step 2: acquiring existing point table information in a real-time database, generating an existing tag table corresponding to the database, and performing step 3;
step 3: acquiring the connection state of the equipment and the OPC-UA server, if the equipment is not connected for data connection, the connection is successful in the step 4, and the connection failure is in the step 11;
step 4: acquiring label information from an OPC-UA server, performing filtering operation, generating an effective label table, and performing step 5;
step 5: comparing the existing tag list with the effective tag list, adding the tags needing to be added, modified and deleted into the corresponding tag processing queues, and performing step 6;
step 6: judging whether the newly added queue is empty, and if so, performing the next operation; otherwise, calling a tag operation function of the real-time database, setting an operation instruction to be newly added, and performing newly added tag operation; if the operation is successful, updating the existing tag table, and performing step 7;
step 7: judging whether the modification queue is empty or not, and if so, performing the next operation; otherwise, calling a tag operation function of the real-time database, setting an operation instruction as modification, and carrying out tag modification operation; if the operation is successful, updating the existing tag table, and returning to the step 8;
step 8: judging whether the deleting queue is empty or not, and if so, performing the next operation; otherwise, calling a tag operation function of the real-time database, setting an operation instruction to be deleted, and performing tag deletion operation; if the operation is successful, updating the existing tag table, and returning to the step 9;
step 9: transmitting an instruction for acquiring data to an OPC-UA server, and acquiring data corresponding to the effective label from the OPC-UA server in a synchronous mode or a subscription mode; if the error is captured, step 11 is performed, otherwise step 10 is invoked;
step 10: calling a snapshot writing function of the real-time database, and synchronizing the collected real-time data into the real-time database; if the data are acquired in a synchronous mode, executing the step 9; if the error is captured, step 11 is performed;
step 11: and acquiring the error information, calling a corresponding processing scheme to process, and writing the error which is not solved into the log to record.
As shown in fig. 2, according to the actual situation of the power plant, after the existing tag table and the valid tag table are generated, the tags exist in the real-time database, the deletion operation of the tags of the database is not allowed, only the modification and the addition operations can be performed, and the deletion operation temporary reservation function is not used. Considering that the tags of the power plant do not frequently perform a large number of adding and modifying operations, the existing tag table always has little change, the data structure of the existing tag table is designed as a hash table, and the effective table is designed as a single list structure. After traversing the labels of the active table and comparing with the existing label table, the labels that need to be added and modified are added to the corresponding task queues. When the device interacts with the real-time database, the interface interacted with the database is abstracted into a universal interface in consideration of the universality of the device, and the factory mode is used for packaging the database interface so that the database interface can be compatible with various databases. In summary, the invention adopts the advantages of the OPC-UA protocol, combines the actual requirements and demands of the field, and provides an automatic data acquisition method based on the OPC-UA protocol, which not only greatly improves the efficiency of data acquisition, but also achieves good effect in the actual application of power plant data acquisition.
Claims (4)
1. An automatic data acquisition method based on OPC-UA protocol is characterized in that: the method comprises the following specific steps:
step 1: acquiring the connection state of the equipment and the real-time database, if the equipment is not connected for data connection, the connection is successful in the step 2, and the connection is failed in the step 11;
step 2: acquiring existing point table information in a real-time database, generating an existing tag table corresponding to the database, and performing step 3;
step 3: acquiring the connection state of the equipment and the OPC-UA server, if the equipment is not connected for data connection, the connection is successful in the step 4, and the connection failure is in the step 11;
step 4: acquiring label information from an OPC-UA server, performing filtering operation, generating an effective label table, and performing step 5;
step 5: comparing the existing tag list with the effective tag list, adding the tags needing to be added, modified and deleted into the corresponding tag processing queues, and performing step 6;
step 6: judging whether the newly added queue is empty, and if so, performing the next operation; otherwise, calling a tag operation function of the real-time database, setting an operation instruction to be newly added, and performing newly added tag operation; if the operation is successful, updating the existing tag table, and performing step 7;
step 7: judging whether the modification queue is empty or not, and if so, performing the next operation; otherwise, calling a tag operation function of the real-time database, setting an operation instruction as modification, and carrying out tag modification operation; if the operation is successful, updating the existing tag table, and returning to the step 8;
step 8: judging whether the deleting queue is empty or not, and if so, performing the next operation; otherwise, calling a tag operation function of the real-time database, setting an operation instruction to be deleted, and performing tag deletion operation; if the operation is successful, updating the existing tag table, and returning to the step 9;
step 9: transmitting an instruction for acquiring data to an OPC-UA server, and acquiring data corresponding to the effective label from the OPC-UA server in a synchronous mode or a subscription mode; if the error is captured, step 11 is performed, otherwise step 10 is invoked;
step 10: calling a snapshot writing function of the real-time database, and synchronizing the collected real-time data into the real-time database; if the data are acquired in a synchronous mode, executing the step 9; if the error is captured, step 11 is performed;
step 11: and acquiring the error information, calling a corresponding processing scheme to process, and writing the error which is not solved into the log to record.
2. The method for automated data collection based on OPC-UA protocol of claim 1 wherein: the detailed process of adding the tag to the real-time database in the step 6 is as follows:
step 6.1: judging whether the newly added tag queue is empty, if so, performing step 7, otherwise, performing step 6.2;
step 6.2: traversing the newly added queue, packaging all the corresponding structures of the newly added tags, calling tag operation functions of the real-time database, and setting the operation instructions as newly added tags; if the new addition is successful, the new addition queue is emptied and the step 7 is carried out, otherwise, the step 6.3 is carried out;
step 6.3: counting error codes and writing the error codes into a log; when the number of errors exceeds a set value, alarm sending operation is carried out; if the set value is not exceeded, performing error processing.
3. The method for automated data collection based on OPC-UA protocol of claim 1 wherein: the detailed procedure of modifying the tag by the real-time database in step 7 is as follows:
step 7.1: judging whether the modified tag queue is empty, if so, performing step 8, otherwise, performing step 7.2;
step 7.2: traversing the update queue, packaging all the structure bodies corresponding to the modification tags, calling tag operation functions of the real-time database, and setting the operation instructions as modification; if the modification is successful, the modification queue is emptied and the step 8 is carried out, otherwise, the step 7.3 is carried out;
step 7.3: counting error codes and writing the error codes into a log; when the number of errors exceeds a set value, alarm sending operation is carried out; if the set value is not exceeded, performing error processing.
4. The method for automated data collection based on OPC-UA protocol of claim 1 wherein: the detailed process of deleting the tag from the real-time database in step 8 is as follows:
step 8.1: judging whether the tag deleting queue is empty, if so, performing step 9, otherwise, performing step 8.2;
step 8.2: traversing the deletion queue, packaging all corresponding structures of the deletion tags, calling tag operation functions of the real-time database, and setting operation instructions as deletion; if the deletion is successful, the deletion queue is emptied and the step 9 is carried out, otherwise, the step 8.3 is carried out;
step 8.3: counting error codes and writing the error codes into a log; when the number of errors exceeds a set value, alarm sending operation is carried out; if the set value is not exceeded, performing error processing.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111299303.4A CN113987047B (en) | 2021-11-04 | 2021-11-04 | OPC-UA protocol-based automatic data acquisition method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111299303.4A CN113987047B (en) | 2021-11-04 | 2021-11-04 | OPC-UA protocol-based automatic data acquisition method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113987047A CN113987047A (en) | 2022-01-28 |
| CN113987047B true CN113987047B (en) | 2024-03-29 |
Family
ID=79746396
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111299303.4A Active CN113987047B (en) | 2021-11-04 | 2021-11-04 | OPC-UA protocol-based automatic data acquisition method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113987047B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106550052A (en) * | 2016-12-08 | 2017-03-29 | 南京富岛信息工程有限公司 | A kind of data acquisition unit and method based on OPC UA |
| WO2018194859A1 (en) * | 2017-04-19 | 2018-10-25 | Microsoft Technology Licensing, Llc | Internet of things pub-sub data publisher |
| CN111142487A (en) * | 2019-12-30 | 2020-05-12 | 浪潮通用软件有限公司 | Equipment data acquisition system based on OPC UA unified architecture protocol |
| CN112099948A (en) * | 2020-09-10 | 2020-12-18 | 西安交通大学 | Method for standardizing digital twin manufacturing unit protocol and integrating industrial big data in real time |
| WO2021153832A1 (en) * | 2020-01-31 | 2021-08-05 | 전자부품연구원 | Advanced operation method, for manufacturing equipment system, using broker-based opc ua pubsub |
-
2021
- 2021-11-04 CN CN202111299303.4A patent/CN113987047B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106550052A (en) * | 2016-12-08 | 2017-03-29 | 南京富岛信息工程有限公司 | A kind of data acquisition unit and method based on OPC UA |
| WO2018194859A1 (en) * | 2017-04-19 | 2018-10-25 | Microsoft Technology Licensing, Llc | Internet of things pub-sub data publisher |
| CN111142487A (en) * | 2019-12-30 | 2020-05-12 | 浪潮通用软件有限公司 | Equipment data acquisition system based on OPC UA unified architecture protocol |
| WO2021153832A1 (en) * | 2020-01-31 | 2021-08-05 | 전자부품연구원 | Advanced operation method, for manufacturing equipment system, using broker-based opc ua pubsub |
| CN112099948A (en) * | 2020-09-10 | 2020-12-18 | 西安交通大学 | Method for standardizing digital twin manufacturing unit protocol and integrating industrial big data in real time |
Non-Patent Citations (1)
| Title |
|---|
| 工业无线网络OPC-UA发布/订阅机制优化研究;梁超;贾宇波;;软件导刊;20200715(07);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113987047A (en) | 2022-01-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2021042790A1 (en) | Master node, slave node, system and method for distributed container cluster mirroring management | |
| CN107729366B (en) | Universal multi-source heterogeneous large-scale data synchronization system | |
| CN113238913B (en) | Intelligent pushing method, device, equipment and storage medium for server faults | |
| CN103123484B (en) | Transformer station's Condition Monitoring Data standardization connecting system and method | |
| CN110457190A (en) | A kind of full link monitoring method, apparatus and system based on block chain | |
| CN112822276B (en) | Substation control layer communication method and system, electronic equipment and storage medium | |
| CN114153920A (en) | Big data edge platform and method | |
| CN108092936A (en) | A kind of Host Supervision System based on plug-in architecture | |
| KR101357135B1 (en) | Apparatus for Collecting Log Information | |
| CN109787844A (en) | A kind of distribution master station communication fault fast positioning system | |
| CN105607606B (en) | A kind of data acquisition device and method based on double mainboard frameworks | |
| CN111046000A (en) | Government data exchange sharing oriented security supervision metadata organization method | |
| CN111913933A (en) | Power grid historical data management method and system based on unified support platform | |
| CN113987047B (en) | OPC-UA protocol-based automatic data acquisition method | |
| CN111914019A (en) | Stable control data management system and method based on block chain technology | |
| CN112612802A (en) | Real-time data middlebox processing method, device and platform | |
| CN117453280A (en) | Code topology and service topology generation method, device, equipment and medium | |
| CN112182065A (en) | Asset management system and method based on automatic acquisition and multi-source import | |
| Huang et al. | Research and application of microservice in power grid dispatching control system | |
| CN110633191A (en) | Method and system for monitoring service health degree of software system in real time | |
| CN114124859B (en) | Intelligent customer service robot of network maintenance platform and maintenance method | |
| CN111897877B (en) | High-performance high-reliability data sharing system and method based on distributed ideas | |
| CN107577789A (en) | Province based on information interactive bus ground artwork interconnected method | |
| CN115878721A (en) | Data synchronization method, device, terminal and computer readable storage medium | |
| CN112800064A (en) | Real-time big data application development method and system based on Confluent community open source edition |
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 |