EP2787455A1 - Device and method for processing history data - Google Patents
Device and method for processing history data Download PDFInfo
- Publication number
- EP2787455A1 EP2787455A1 EP20140162406 EP14162406A EP2787455A1 EP 2787455 A1 EP2787455 A1 EP 2787455A1 EP 20140162406 EP20140162406 EP 20140162406 EP 14162406 A EP14162406 A EP 14162406A EP 2787455 A1 EP2787455 A1 EP 2787455A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- data
- record
- collected
- stored
- collecting
- 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.)
- Withdrawn
Links
Images
Classifications
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
- G06F17/40—Data acquisition and logging
Definitions
- the present disclosure relates to a device and method for processing history data.
- a supervisory control and data acquisition (SCADA) system is a system in which a remote terminal unit collects receives ⁇ records ⁇ displays an analog or digital signal on a communication path and a central control system monitors and controls the remote terminal unit.
- SCADA supervisory control and data acquisition
- the system may control and monitor many types of remote facilities and devices such as a power generation ⁇ power transmission and distribution facility ⁇ a petrochemistry plant, a steel making process, and a factory automation facility, in a centralized manner.
- a power generation ⁇ power transmission and distribution facility ⁇ a petrochemistry plant, a steel making process, and a factory automation facility, in a centralized manner.
- the SCADA system needs management and control on massive data collected from the remote terminal unit and thus builds a database (DB) that may store the massive data.
- DB database
- Fig. 1 illustrates a typical structure of a DB for storing the massive data.
- the massive data collected through a data collecting unit of the SCADA system is sequentially accumulated and stored in one record over time as shown in FIG. 1 .
- the history server checks Tag ID, Timestamp, Value and Quality information, sequentially accumulates input data and stores the data in one record.
- Embodiments provide a method and device for processing history data that may efficiently store and manage a plurality of sets that increases over time in processing the history data.
- Embodiments also provide a method and device for processing history data that enables stored history data to be searched rapidly and easily.
- a method of processing history data includes collecting data; checking state information on a database (DB) record for the collected data; and storing the collected data in a record based on the checked state information, wherein the data stored in the record is stored in the form of a set of data that includes time offset, value and quality.
- DB database
- Record information may include fields: times to start and end collecting data, number of sets of data, and data.
- a new record may be generated to store the set of data.
- a new record may be generated to store the set of data.
- the method may further include temporarily storing the collected data, and deleting the temporarily stored data if the data is stored in the record.
- a device for processing history data includes a data collecting unit collecting data generated from devices to be controlled and monitored; a data processing unit generating the collected data in the form of a set of data that includes time offset, value and quality; and a database (DB) storing collected data generated in the set of data.
- DB database
- the DB may include a first storage unit storing information for collecting history data; a second storage unit temporarily storing data collected by the data collecting unit; and a third storage unit storing a set of data generated by the data processing unit.
- the third storage unit may store the collected data, based on the size of a set of data or a time offset, in a set of data in an existing record, or may generate a new record and store the new record in a set of data.
- the record may include a time to collect data, a number of pieces of collected data, data and data identifier (ID).
- ID data identifier
- the data ID in the record may be set as a DWORD-type serial number.
- the number of pieces of data may be generated by counting a number of WORD-type TVQs.
- the data processing unit may generate a set of data to store the collected data in a BOLD type.
- Fig. 2 is a block diagram of a history server to which an embodiment is applied.
- a history server 100 to which an embodiment is applied may include a data collecting unit 110, a data processing unit 120, a database (DB) 130 and a backup processing unit 140.
- DB database
- the data collecting unit 110 may receive data generated from devices to be controlled and monitored, in real time or regularly.
- the data collecting unit 110 may include at least one module that may be connected to the devices in a wired manner or wirelessly.
- the data collecting unit 110 may collect data in real time or regularly while being connected to the devices in a wired manner or wirelessly.
- the data processing unit 120 may perform processing, comparing and calculating on data stored in the DB 130 through the data collecting unit 110.
- the data processing unit 120 may continuously store history data by tag, a plurality of sets of data (Time Offset, Value, Quality: TVQ) in a BLOB-type field.
- the DB 130 may temporarily or permanently store data received from the data collecting unit 110.
- the DB 130 may include a first storage unit 131, a second storage unit 132, and a third storage unit 133.
- the first storage unit 131 has configuration information that a history server needs when collecting history data. It may store information on a collecting unit for collecting tag data, tag information, and configuration information for managing history data.
- the second storage unit 132 may perform a function of temporarily storing data collected through the data collecting unit 110. According to an embodiment, it is possible to temporarily store data collected through the data collecting unit 110 in the second storage unit 132, update record data and then delete data stored in the second storage unit 132.
- the third storage unit 133 may sequentially store sets of data according to an embodiment. That is, the third storage unit 133 may store a set of data in an existing record or generate a set of data for data collected through the data collecting unit 110, based on the size or time offset of the set of data.
- the DB 120 is configured as e.g., a plurality of storage units, the number of storages units may be variable and the DB 120 may be configured as a storage unit.
- the backup processing unit 140 may back up collected data, and data stored in the record.
- the backed-up data may be deleted only by a compulsory delete request signal.
- Fig. 3 is a flow chart for explaining the operation of processing data by a history server according to an embodiment
- Fig. 4 illustrates how history data is stored in a DB of a history server according to an embodiment.
- the data collecting unit 110 may collect data transmitted from the remote terminal unit in real time or regularly in step S310.
- the collected data may be temporarily stored in the second storage unit 132 of the DB 130 according to the control of the data processing unit 120 in step S320.
- the data processing unit 120 may read and process data temporarily stored in the second storage unit 132 of the DB 130 and generate a set of data to store the processed data in a BOLD type.
- the data processing unit 120 may check history data on the processed collected data in step S340.
- the data processing unit 120 may determine based on the checked history data whether the size of a record including a plurality of sets of data is less than or equal to 1 KB or whether a time offset exceeds the maximum value of DWORD, in step S350.
- the set of data may include time offset, value and quality.
- the data processing unit 120 may update data on an existing record according to a determination result in step S360.
- step S70 it is possible to generate a new record in step S70 and it is possible to update data on a generated record in step S380.
- the data processing unit 120 may check history data among data stored in the DB 130, generated and store a record on corresponding history data as shown in Fig. 4 .
- a record may include times to start and end collecting data, data count representing the number of pieces of data collected in a collection time, collected data, and tag ID of collected data.
- An ID included in a record may be set as a DWORD-type serial number.
- the number of pieces of data collected between the times start and end collecting data may be generated by counting the number of WORD-type TVQs.
- Collected data corresponding to the number of BLOB-type TVQ sets may be recorded in the data field of the record.
- an offset defining a time difference between an initial data collection time (first data collection time) and a following data collection time (second data collection time) may be recorded in a DWORD type.
- the unit of the time offset may be ms.
- a value for the data of the TVQ set may be recorded in a FLOAT type and quality may be recorded in a WORD type.
- data is collected for a certain time and the collected data is recorded as the TVQ set in the record. Also, when the TVQ set exceeds a certain capacity or the time offset is equal to or greater than a threshold, it is possible to generate a new record and store data.
- the data processing unit 120 may delete temporarily stored collected data in order to optimize the capacity of the DB when storing data is completed.
- Embodiments are mainly described above. However, they are just examples and do not limit the present invention. A person skilled in the art may appreciate that several variations and applications not presented above may be made without departing from the essential characteristic of embodiments. For example, each component specifically represented in embodiments may vary. In addition, it should be construed that differences related to such a variation and such an application are included in the scope of the present invention defined in the following claims.
Landscapes
- Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Signal Processing (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Medical Informatics (AREA)
- General Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Mathematical Physics (AREA)
- Databases & Information Systems (AREA)
- Computer Hardware Design (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
- The present disclosure relates to a device and method for processing history data.
- A supervisory control and data acquisition (SCADA) system is a system in which a remote terminal unit collects receives · records · displays an analog or digital signal on a communication path and a central control system monitors and controls the remote terminal unit.
- For example, the system may control and monitor many types of remote facilities and devices such as a power generation · power transmission and distribution facility · a petrochemistry plant, a steel making process, and a factory automation facility, in a centralized manner.
- The SCADA system needs management and control on massive data collected from the remote terminal unit and thus builds a database (DB) that may store the massive data.
-
Fig. 1 illustrates a typical structure of a DB for storing the massive data. - Referring to
FIG. 1 , the massive data collected through a data collecting unit of the SCADA system is sequentially accumulated and stored in one record over time as shown inFIG. 1 . - That is, when typically storing data received through the data collecting unit in a DB of a history server, the history server checks Tag ID, Timestamp, Value and Quality information, sequentially accumulates input data and stores the data in one record.
- Thus, when managing data with a typical DB, there may be a limitation in that a velocity and time increases when storing and searching massive data as one set of data (Tag ID, Timestamp, Value and Quality) per record is stored in a DB table..
- Embodiments provide a method and device for processing history data that may efficiently store and manage a plurality of sets that increases over time in processing the history data.
- Embodiments also provide a method and device for processing history data that enables stored history data to be searched rapidly and easily.
- In one embodiment, a method of processing history data, the method includes collecting data; checking state information on a database (DB) record for the collected data; and storing the collected data in a record based on the checked state information, wherein the data stored in the record is stored in the form of a set of data that includes time offset, value and quality.
- Record information may include fields: times to start and end collecting data, number of sets of data, and data.
- When the set of data is stored in a record and the number of the set of data exceeds a certain number, a new record may be generated to store the set of data.
- When the set of data is stored in a record and a time offset exceeds a preset maximum reference value, a new record may be generated to store the set of data.
- The method may further include temporarily storing the collected data, and deleting the temporarily stored data if the data is stored in the record.
- In another embodiment, a device for processing history data includes a data collecting unit collecting data generated from devices to be controlled and monitored; a data processing unit generating the collected data in the form of a set of data that includes time offset, value and quality; and a database (DB) storing collected data generated in the set of data.
- The DB may include a first storage unit storing information for collecting history data; a second storage unit temporarily storing data collected by the data collecting unit; and a third storage unit storing a set of data generated by the data processing unit.
- The third storage unit may store the collected data, based on the size of a set of data or a time offset, in a set of data in an existing record, or may generate a new record and store the new record in a set of data.
- The record may include a time to collect data, a number of pieces of collected data, data and data identifier (ID).
- The data ID in the record may be set as a DWORD-type serial number.
- The number of pieces of data may be generated by counting a number of WORD-type TVQs.
- The data processing unit may generate a set of data to store the collected data in a BOLD type.
- The details of one or more embodiments are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.
-
-
Fig. 1 illustrates a typical structure of a DB for storing massive data. -
Fig. 2 is a block diagram of a history server to which an embodiment is applied. -
Fig. 3 is a flow chart for explaining the operation of processing data by a history server according to an embodiment. -
Fig. 4 illustrates how history data is stored in a DB of a history server according to an embodiment. - The terms or words used in the detailed description and claims should not be imitatively construed as typical meanings or meanings indicated in dictionaries but should be construed as meanings and concepts matching the technical spirit of the present invention based on the principle that the inventor may properly define the concepts of terms in order to describe his or her invention in the best mode.
- Thus, since embodiments described in the detailed description and configurations shown in the drawings are merely examples and do not cover all the technical spirits of an embodiment, it should be understood that there may be various equivalents and variations that may replace them upon filing the present application.
-
Fig. 2 is a block diagram of a history server to which an embodiment is applied. - Referring to
Fig. 2 , ahistory server 100 to which an embodiment is applied may include adata collecting unit 110, adata processing unit 120, a database (DB) 130 and abackup processing unit 140. - The
data collecting unit 110 may receive data generated from devices to be controlled and monitored, in real time or regularly. Thedata collecting unit 110 may include at least one module that may be connected to the devices in a wired manner or wirelessly. Thedata collecting unit 110 may collect data in real time or regularly while being connected to the devices in a wired manner or wirelessly. - The
data processing unit 120 may perform processing, comparing and calculating on data stored in theDB 130 through thedata collecting unit 110. Thedata processing unit 120 according to an embodiment may continuously store history data by tag, a plurality of sets of data (Time Offset, Value, Quality: TVQ) in a BLOB-type field. - The DB 130 may temporarily or permanently store data received from the
data collecting unit 110. The DB 130 according to an embodiment may include afirst storage unit 131, asecond storage unit 132, and athird storage unit 133. - The
first storage unit 131 has configuration information that a history server needs when collecting history data. It may store information on a collecting unit for collecting tag data, tag information, and configuration information for managing history data. - The
second storage unit 132 may perform a function of temporarily storing data collected through thedata collecting unit 110. According to an embodiment, it is possible to temporarily store data collected through thedata collecting unit 110 in thesecond storage unit 132, update record data and then delete data stored in thesecond storage unit 132. - The
third storage unit 133 may sequentially store sets of data according to an embodiment. That is, thethird storage unit 133 may store a set of data in an existing record or generate a set of data for data collected through thedata collecting unit 110, based on the size or time offset of the set of data. - Although the DB 120 according to an embodiment of the present invention is configured as e.g., a plurality of storage units, the number of storages units may be variable and the
DB 120 may be configured as a storage unit. - The
backup processing unit 140 may back up collected data, and data stored in the record. The backed-up data may be deleted only by a compulsory delete request signal. - An operation of processing data by a history server with such a configuration is described in detail with reference to
Figs. 3 and4 . -
Fig. 3 is a flow chart for explaining the operation of processing data by a history server according to an embodiment, andFig. 4 illustrates how history data is stored in a DB of a history server according to an embodiment. - Referring to
Figs. 3 and4 , thedata collecting unit 110 may collect data transmitted from the remote terminal unit in real time or regularly in step S310. - The collected data may be temporarily stored in the
second storage unit 132 of the DB 130 according to the control of thedata processing unit 120 in step S320. - The
data processing unit 120 may read and process data temporarily stored in thesecond storage unit 132 of the DB 130 and generate a set of data to store the processed data in a BOLD type. - The
data processing unit 120 may check history data on the processed collected data in step S340. - The
data processing unit 120 may determine based on the checked history data whether the size of a record including a plurality of sets of data is less than or equal to 1 KB or whether a time offset exceeds the maximum value of DWORD, in step S350. - The set of data may include time offset, value and quality.
- The
data processing unit 120 may update data on an existing record according to a determination result in step S360. - Alternatively, it is possible to generate a new record in step S70 and it is possible to update data on a generated record in step S380.
- That is, the
data processing unit 120 may check history data among data stored in theDB 130, generated and store a record on corresponding history data as shown inFig. 4 . - As shown in
Fig. 4A , a record may include times to start and end collecting data, data count representing the number of pieces of data collected in a collection time, collected data, and tag ID of collected data. - An ID included in a record may be set as a DWORD-type serial number. The number of pieces of data collected between the times start and end collecting data may be generated by counting the number of WORD-type TVQs. Collected data corresponding to the number of BLOB-type TVQ sets may be recorded in the data field of the record. For example, for data of the TVQ set recorded in the data field as shown in
Fig. 4B , an offset defining a time difference between an initial data collection time (first data collection time) and a following data collection time (second data collection time) may be recorded in a DWORD type. The unit of the time offset may be ms. Also, a value for the data of the TVQ set may be recorded in a FLOAT type and quality may be recorded in a WORD type. - Thus, as described above, data is collected for a certain time and the collected data is recorded as the TVQ set in the record. Also, when the TVQ set exceeds a certain capacity or the time offset is equal to or greater than a threshold, it is possible to generate a new record and store data.
- The
data processing unit 120 may delete temporarily stored collected data in order to optimize the capacity of the DB when storing data is completed. - Embodiments are mainly described above. However, they are just examples and do not limit the present invention. A person skilled in the art may appreciate that several variations and applications not presented above may be made without departing from the essential characteristic of embodiments. For example, each component specifically represented in embodiments may vary. In addition, it should be construed that differences related to such a variation and such an application are included in the scope of the present invention defined in the following claims.
Claims (12)
- A method of processing history data, the method comprising:collecting data;checking state information on a database (DB) record for the collected data; andstoring the collected data in a record based on the checked state information,wherein the data stored in the record is stored in the form of a set of data that includes time offset, value and quality.
- The method according to claim 1, wherein record information comprises fields: times to start and end collecting data, number of sets of data, and data.
- The method according to claim 1, wherein when the set of data is stored in a record and the number of the set of data exceeds a certain number, a new record is generated to store the set of data.
- The method according to claim 1, wherein when the set of data is stored in a record and a time offset exceeds a preset maximum reference value, a new record is generated to store the set of data.
- The method according to claim 1, further comprising temporarily storing the collected data, and deleting the temporarily stored data if the data is stored in the record.
- A device for processing history data, the device comprising:a data collecting unit collecting data generated from devices to be controlled and monitored;a data processing unit generating the collected data in the form of a set of data that includes time offset, value and quality; anda database (DB) storing collected data generated in the set of data.
- The device according to claim 6, wherein the DB comprises:a first storage unit storing information for collecting history data;a second storage unit temporarily storing data collected by the data collecting unit; anda third storage unit storing a set of data generated by the data processing unit.
- The device according to claim 7, wherein the third storage unit stores the collected data, based on the size of a set of data or a time offset, in a set of data in an existing record, or generates a new record and stores the new record in a set of data.
- The device according to claim 8, wherein the record comprises a time to collect data, a number of pieces of collected data, data and data identifier (ID).
- The device according to claim 9, wherein the data ID in the record is set as a DWORD-type serial number.
- The device according to claim 9, wherein the number of pieces of data is generated by counting a number of WORD-type TVQs.
- The device according to claim 6, wherein the data processing unit generates a set of data to store the collected data in a BOLD type.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR20130035136A KR101442968B1 (en) | 2013-04-01 | 2013-04-01 | Apparatus and method for processing and storing of Archive data |
Publications (1)
Publication Number | Publication Date |
---|---|
EP2787455A1 true EP2787455A1 (en) | 2014-10-08 |
Family
ID=50513674
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP20140162406 Withdrawn EP2787455A1 (en) | 2013-04-01 | 2014-03-28 | Device and method for processing history data |
Country Status (3)
Country | Link |
---|---|
US (1) | US20140297691A1 (en) |
EP (1) | EP2787455A1 (en) |
KR (1) | KR101442968B1 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR102375899B1 (en) * | 2015-05-21 | 2022-03-18 | 엘에스일렉트릭(주) | Thermoelectric conversion system using waste heat and nanoparticle |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5754449A (en) * | 1995-04-25 | 1998-05-19 | Instrumented Sensor Technology, Inc. | Method and apparatus for recording time history data of physical variables |
US6272445B1 (en) * | 1998-06-05 | 2001-08-07 | Trendview Recorders Limited | Data logging |
US20050240359A1 (en) * | 2002-02-28 | 2005-10-27 | Frederick Jesse R | In-place dynamically re-sizeable persistent historical database |
US20120011178A1 (en) * | 2010-07-09 | 2012-01-12 | Navteq North America, Llc | Method and system for handling binary large objects |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5403639A (en) * | 1992-09-02 | 1995-04-04 | Storage Technology Corporation | File server having snapshot application data groups |
US9235955B2 (en) * | 2000-12-22 | 2016-01-12 | Bally Gaming, Inc. | Universal game monitoring unit and system |
US7035877B2 (en) * | 2001-12-28 | 2006-04-25 | Kimberly-Clark Worldwide, Inc. | Quality management and intelligent manufacturing with labels and smart tags in event-based product manufacturing |
US7032816B2 (en) * | 2001-12-28 | 2006-04-25 | Kimberly-Clark Worldwide, Inc. | Communication between machines and feed-forward control in event-based product manufacturing |
US7357298B2 (en) * | 2001-12-28 | 2008-04-15 | Kimberly-Clark Worldwide, Inc. | Integrating event-based production information with financial and purchasing systems in product manufacturing |
US7380213B2 (en) * | 2001-12-28 | 2008-05-27 | Kimberly-Clark Worldwide, Inc. | User interface for reporting event-based production information in product manufacturing |
US8799113B2 (en) * | 2001-12-28 | 2014-08-05 | Binforma Group Limited Liability Company | Quality management by validating a bill of materials in event-based product manufacturing |
JP4387087B2 (en) * | 2002-07-25 | 2009-12-16 | 三洋電機株式会社 | Data storage device |
US7222133B1 (en) * | 2004-02-05 | 2007-05-22 | Unisys Corporation | Method for reducing database recovery time |
US7467163B1 (en) * | 2006-02-10 | 2008-12-16 | Unisys Corporation | System and method to manipulate large objects on enterprise server data management system |
US20110028827A1 (en) * | 2009-07-28 | 2011-02-03 | Ranganatha Sitaram | Spatiotemporal pattern classification of brain states |
US8271719B2 (en) * | 2009-10-29 | 2012-09-18 | Freescale Semiconductor, Inc. | Non-volatile memory controller device and method therefor |
WO2011154900A2 (en) * | 2010-06-10 | 2011-12-15 | Hach Company | Server monitoring of flow and sampling apparatus and/or logger |
US8850536B2 (en) * | 2011-08-05 | 2014-09-30 | Safefaces LLC | Methods and systems for identity verification in a social network using ratings |
-
2013
- 2013-04-01 KR KR20130035136A patent/KR101442968B1/en not_active IP Right Cessation
-
2014
- 2014-03-28 EP EP20140162406 patent/EP2787455A1/en not_active Withdrawn
- 2014-03-31 US US14/230,893 patent/US20140297691A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5754449A (en) * | 1995-04-25 | 1998-05-19 | Instrumented Sensor Technology, Inc. | Method and apparatus for recording time history data of physical variables |
US6272445B1 (en) * | 1998-06-05 | 2001-08-07 | Trendview Recorders Limited | Data logging |
US20050240359A1 (en) * | 2002-02-28 | 2005-10-27 | Frederick Jesse R | In-place dynamically re-sizeable persistent historical database |
US20120011178A1 (en) * | 2010-07-09 | 2012-01-12 | Navteq North America, Llc | Method and system for handling binary large objects |
Also Published As
Publication number | Publication date |
---|---|
KR101442968B1 (en) | 2014-09-25 |
US20140297691A1 (en) | 2014-10-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111158977B (en) | Abnormal event root cause positioning method and device | |
US10176208B2 (en) | Processing time series data from multiple sensors | |
US11960443B2 (en) | Block data storage system in an event historian | |
US9842134B2 (en) | Data query interface system in an event historian | |
US9600389B2 (en) | Generating performance and capacity statistics | |
US20120271962A1 (en) | Achieving Lossless Data Streaming in a Scan Based Industrial Process Control System | |
CN115757363B (en) | Multi-level management method and system for three-dimensional cadastral database | |
US7853568B2 (en) | High speed data historian | |
CN107491458B (en) | Method, device and system for storing time series data | |
CN112559475A (en) | Data real-time capturing and transmitting method and system | |
CN104778177A (en) | Data processing method and device | |
US20130204913A1 (en) | File list generation method, system, and program, and file list generation device | |
CN109861843B (en) | Method, device and equipment for completely collecting and confirming log files | |
EP2787455A1 (en) | Device and method for processing history data | |
CN111737233A (en) | Data monitoring method and device | |
CN112486911A (en) | Robot operation data collection management method and device, storage medium and terminal | |
CN113868096B (en) | Asynchronous data transmission monitoring method and device, electronic equipment and storage medium | |
KR102382134B1 (en) | Attack detection device, attack detection method, and attack detection program | |
CN109143878B (en) | Remote signaling message and SOE message processing method for multi-channel acquisition channel | |
CN112559645A (en) | Processing method and device for mass operation and maintenance data | |
CN117609315B (en) | Data processing method, device, equipment and readable storage medium | |
CN112506933B (en) | High-speed multichannel time sequence data storage method | |
JP7170523B2 (en) | Data management device, data management method, computer program and data management system | |
US20170212938A1 (en) | Method and apparatus for accessing and calculating industrial information | |
US11347764B1 (en) | Time series table compression |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20140328 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
R17P | Request for examination filed (corrected) |
Effective date: 20141126 |
|
RBV | Designated contracting states (corrected) |
Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
17Q | First examination report despatched |
Effective date: 20151204 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN |
|
18W | Application withdrawn |
Effective date: 20160908 |