A centralized data management method, device and equipment based on cache comparison linkage

Abstract

The present disclosure relates to the technical field of new energy centralized control, and specifically discloses a centralized control data management method, device and equipment based on cache comparison linkage. The present scheme maintains a full-measuring-point cache table in the memory of the centralized control side as the only comparison pivot for data processing. After unified analysis of the sudden change data packet and the total call data packet uploaded by the station, the cache table is compared. Based on the single comparison result, multi-path linkage processing is synchronously performed: when the measuring point value changes, it is immediately pushed to the monitoring interface, the marked data is pending for persistence and is directed to push to the subscribed alarm center, and the real-time calculation background program; when the measuring point value does not change, only the cache timestamp is refreshed. At the same time, the cache timestamp is relied on to realize the periodic storage of measuring points and the identification of communication timeout exceptions. The present scheme cancels the pre-requisite of data warehousing, greatly reduces the interface refresh delay and the write pressure of the time series database, improves the response efficiency of various business programs, and is suitable for the centralized monitoring scene of wind, light and storage multi-stations.

Description

Technical Field

[0001] This disclosure relates to the field of new energy centralized control technology, and in particular to a centralized control data management method, device and equipment based on cache comparison linkage. Background Technology

[0002] In the operation and monitoring of the new energy centralized control system, various sensors and measurement and control devices on the site side (also known as the power plant side) continuously collect data from measurement points at a frequency of seconds or even milliseconds, and then package the data and send it to the centralized control side. After receiving the data packets, the centralized control side needs to parse, display, and persistently store the data.

[0003] In related technologies, the centralized control side typically needs to write all the measurement point data uploaded by the field station to a time-series database first, and then the monitoring interface reads the data from the time-series database or cache for refresh and display. Alarm, report and other data processing programs also need to query the latest data from the time-series database to complete their respective business logic. This serial data flow mode of "first enter the database, then read" has problems when facing a large amount of sudden change data and general call data in the new energy centralized control scenario. It has the problem of interface push, data persistence and program consumption being disconnected and waiting for each other, resulting in high overall response latency, low resource utilization, and affecting the real-time performance and availability of the centralized control system. Summary of the Invention

[0004] To overcome the problems existing in related technologies, this disclosure provides a centralized control data management method, apparatus and equipment based on cache comparison linkage.

[0005] According to a first aspect of the present disclosure, a centralized control data management method based on cache comparison linkage is provided, applied to the centralized control side. The method includes: maintaining a full measurement point cache table on the centralized control side that corresponds one-to-one with each measurement point on the field station side; receiving and parsing mutation data packets and general call data packets uploaded by the field station side to generate measurement point records to be processed; comparing the measurement point records to be processed with the corresponding cache records in the full measurement point cache table; and synchronously performing the following linkage operations based on the same comparison result: when the value of the measurement point record to be processed is different from the value of the cache record, updating the value of the cache record to the value of the measurement point record to be processed, updating the first update time and the last update time of the cache record, and simultaneously pushing the updated measurement point value to the monitoring interface on the centralized control side, marking the measurement point record to be processed as pending persistence, and pushing the updated measurement point value to the data processing program subscribing to the measurement point; and writing the measurement point record marked as pending persistence into a time series database.

[0006] According to a second aspect of the present disclosure, a centralized control data management device based on cache comparison linkage is provided, disposed on the centralized control side, the device comprising: The cache maintenance unit is configured to maintain a full measurement point cache table on the central control side that corresponds one-to-one with each measurement point on the field station side. The full measurement point cache table resides in the memory of the central control side and is used to store the latest value and update time of each measurement point. The parsing and comparison unit is configured to receive and parse the mutation data packets and general call data packets uploaded by the site side, generate a test point record to be processed, and compare the test point record to be processed with the corresponding cache record in the full test point cache table; The linkage execution unit is configured to synchronously perform the following operations based on the same comparison result: when the value of the measurement point record to be processed is different from the value of the cache record, update the value of the cache record to the value of the measurement point record to be processed, and update the first update time and the last update time of the cache record. At the same time, push the updated measurement point value to the monitoring interface on the centralized control side in real time, mark the measurement point record to be processed as pending persistence, and push the updated measurement point value to the data processing program that subscribes to the measurement point; when the value of the measurement point record to be processed is the same as the value of the cache record, only update the last update time of the cache record. The persistence unit is configured to write measurement point records marked as pending persistence status to the time series database.

[0007] According to a third aspect of the present disclosure, an electronic device is provided, including a processor and a memory, wherein the processor executes the method as described in the first aspect by invoking a computer program in the memory.

[0008] According to a fourth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the method described in the first aspect.

[0009] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects: By constructing a full measurement point cache table on the centralized control side that corresponds one-to-one with each measurement point on the field station side, and using this cache table as the sole data comparison and push hub before data is stored in the database, when a mutation data packet or general call data packet is received from the field station, a single comparison can simultaneously determine three action paths: "whether to push to the interface, whether to mark for persistence, and whether to push to the subscription program." This achieves synchronous linkage between interface push, data persistence, and program consumption, breaking the serial dependency of "first store in the database, then read" in related technologies. This allows interface push, data persistence, and program consumption to proceed synchronously, avoiding mutual waiting issues, improving overall response speed, resource utilization, and the real-time performance and availability of the centralized control system.

[0010] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0011] The accompanying drawings, which are incorporated in and form part of this disclosure, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0012] Figure 1 This disclosure is a schematic diagram of the architecture of a centralized control system according to an exemplary embodiment.

[0013] Figure 2 This is a schematic flowchart illustrating a centralized control data management method based on cache comparison linkage according to an exemplary embodiment of the present disclosure.

[0014] Figure 3 This disclosure is a block diagram of a centralized control data management device based on cache comparison linkage according to an exemplary embodiment.

[0015] Figure 4 This is a schematic block diagram of an electronic device according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0016] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0017] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The singular forms “a,” “the,” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0018] It should be understood that although the terms first, second, third, etc., may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0019] In related technologies, the control side typically needs to first write all the measurement point data uploaded by the site side into a time-series database, and then the monitoring interface reads the data from the time-series database or cache for refresh and display. Alarm, report, and other data processing programs also need to query the latest data from the time-series database to complete their respective business logic. This "first in, then read" serial data flow mode has the following prominent problems when facing a large amount of sudden changes and general call data in new energy centralized control scenarios: First, the monitoring interface has a high refresh latency. Data must first be written to the time series database before it can be read by the monitoring interface. The write operation of the time series database involves disk I / O. Even high-performance time series databases have millisecond-level latency. In scenarios with a large amount of data being written concurrently, the time when the monitoring interface perceives data changes is significantly delayed compared to the actual time when the data is generated. Maintenance personnel cannot grasp the status of the site equipment in real time.

[0020] Second, redundant writing leads to resource waste. There are a large number of duplicate reports of "unchanged values" in the measurement data at the site. Especially during full-scale testing, the values ​​of most measurement points have not changed, but the relevant technologies still write all these unchanged data into the time series database, resulting in a huge amount of written data. This not only occupies network bandwidth and disk space, but also increases the processing burden of the time series database.

[0021] Third, data processing programs such as alarms and reports have low response efficiency. These programs usually obtain the latest data by polling the time-series database or subscribing to the database change log. They are also limited by the "first-in-database" latency bottleneck and cannot be triggered the moment the data arrives at the central control side.

[0022] Fourth, the processing logic for mutation data and general call data is separate. Currently, most companies in the industry use two independent logics to process mutation data and general call full data separately: mutation data goes through an incremental update channel, while general call data goes through a full coverage channel. The two sets of data benchmarks are inconsistent, which can easily cause deviations in the measurement point data when switching channels or processing concurrently.

[0023] Fifth, timeout detection for measurement points is scattered across the field stations, and timeout judgments are mostly deployed on field station gateways or terminal devices. The centralized control station lacks a unified measurement point status judgment capability based on global caching, making it difficult to achieve centralized timeout management across field stations and channels. Therefore, the data flow method on the centralized control side in related technologies suffers from the problems of fragmentation and mutual waiting among interface push, data persistence, and program consumption, resulting in high overall response latency, low resource utilization, and affecting the real-time performance and availability of the centralized control system.

[0024] In a new energy centralized control system, to achieve centralized monitoring of multiple subordinate stations, the central control station needs to receive measurement data from each station in real time and simultaneously complete three tasks: data display, storage, and distribution. The relevant technical parameters involved in this disclosure, such as the first preset duration, the second preset duration, and the batch write cycle, are merely illustrative examples and can be flexibly configured according to on-site operational needs during actual deployment, and do not constitute a limitation on the scope of protection of this disclosure.

[0025] Figure 1 This is a schematic diagram of the architecture of a centralized control system according to an embodiment of the present disclosure.

[0026] like Figure 1 As shown, the centralized control system includes: a station-side server 110 (hereinafter referred to as the station side), a centralized control-side server 120 (hereinafter referred to as the centralized control side), a time-series database 130, and a monitoring interface ( Figure 1 (Not shown in the image).

[0027] The number of the site-side servers 110 can be multiple, and they are set up in different new energy sites (such as wind farms, photovoltaic power stations, and energy storage power stations). They are used to collect measurement data (including telemetry and teleindication) from sensors and measurement and control devices set up in the power station, and package the data and send it to the central control side server 120.

[0028] The central control server 120 receives data packets from multiple site-side servers 110 and runs the data management method disclosed herein. The central control server 120 internally maintains a full measurement point cache table, which corresponds one-to-one with all measurement points in the site, storing the latest value, first update time, and last update time for each measurement point. The full measurement point cache table is constructed by loading the latest values ​​of each measurement point at the last timestamp from the time-series database 130 during system initial startup. After construction, it resides permanently in the memory of the central control server, serving as the comparison benchmark and push hub for all subsequent data processing. It should be noted that the "full measurement point cache table" of this disclosure is a global, permanently resident snapshot of all measurement points in the central control master station's memory, distinct from single-point temporary caches, database hotspot caches, or site-side local caches in related technologies, which lack the ability for global comparison benchmarks and unified linkage.

[0029] The time series database 130 is used to receive and store time series data records transmitted from the central control side server 120, forming a complete historical data archive of the station measurement points.

[0030] The monitoring interface is used to display the operating status of the station equipment in real time. The screen is refreshed by receiving the changing measurement point values ​​pushed by the central control side server 120.

[0031] In addition, the centralized control side is also equipped with alarm programs, reporting programs and other data processing programs, which obtain notifications of changes in measurement point values ​​through subscription.

[0032] The field station typically sends data packets to the central control unit in two situations: first, when a measurement point's value undergoes a sudden change, the field station proactively packages the data of the changed measurement point into a sudden change data packet and uploads it to the central control unit; second, when the field station receives a general call command from the central control unit, the field station packages the latest values ​​of all measurement points into a general call data packet and uploads it to the central control unit. It is important to note that in related technologies, sudden change data and general call data typically employ two independent processing logics: sudden change data uses an incremental update channel, while general call data uses a full coverage channel. The two sets of data benchmarks are inconsistent, which can easily cause data deviations during channel switching or concurrent processing. In this disclosure, however, the central control unit uses the same comparison and linkage process for both sudden change data packets and general call data packets: a unified comparison with the full measurement point cache table, unified triggering of linkage push and persistent marking, eliminating the risk of inconsistency between the two channels from the source.

[0033] Figure 2 This is a schematic flowchart illustrating a centralized control data management method based on cache comparison linkage according to an embodiment of the present disclosure. The method can be executed by a terminal, which can be configured as follows: Figure 1 The control server 120 in the system shown.

[0034] like Figure 2 As shown, the method includes: In step S201, a full measurement point cache table is maintained on the central control side, corresponding one-to-one with each measurement point on the field station side.

[0035] In step S202, the data packets uploaded by the station side are parsed to generate test point records to be processed, and the test point records to be processed are compared with the corresponding cache records in the full test point cache table.

[0036] In step S203, based on the same comparison result, a linkage operation is executed synchronously. The linkage operation includes: when the value of the measurement point record to be processed is different from the value of the cache record, updating the value of the cache record to the value of the measurement point record to be processed, updating the first update time and the last update time of the cache record, and simultaneously pushing the updated measurement point value to the monitoring interface on the centralized control side in real time, marking the measurement point record to be processed as pending persistence, and pushing the updated measurement point value to the data processing program that subscribes to the measurement point.

[0037] In step S204, the measurement point records marked as to be persisted are written into the time series database.

[0038] In some embodiments, in step S201, the full measurement point cache table is constructed by loading the latest values ​​of each measurement point at the last timestamp from the time-series database during initial startup. During construction, the latest values ​​of all measurement points at the last timestamp in the time-series database are traversed, and each value is written to the full measurement point cache table. The first update time and last update time of each measurement point are initialized to that timestamp. After construction, the full measurement point cache table resides in the memory of the central control side for use in the parsing and comparison of all subsequent data packets.

[0039] In some embodiments, each cached record in the full measurement point cache table may contain the following fields: measurement point identifier, latest value, first update time, and last update time.

[0040] The measurement point identifier may include, but is not limited to, the station code, channel number, and information object address, and is used to uniquely identify a measurement point at the station level. The first update time is the time when the measurement point value last changed; the last update time is the time when the measurement point value was last compared (regardless of whether the value changed).

[0041] In some embodiments, in step S202, the data packets uploaded by the station side are parsed to obtain each measurement point data in the data packets, forming a measurement point record to be processed. Each measurement point record to be processed includes at least a measurement point identifier and a measurement point value.

[0042] The process involves comparing the measurement point record to be processed with the cached records in the full measurement point cache table. Specifically, this includes: searching for a cached record with the same identifier in the full measurement point cache table based on the measurement point identifier of the measurement point record to be processed; if found, comparing the measurement point value of the measurement point record to be processed with the latest value of the cached record; if not found (e.g., a new measurement point has been added to the site), creating a new cached record in the full measurement point cache table, using the value of the measurement point record to be processed as the latest value of the cached record, and initializing the first update time and the last update time with the acquisition time corresponding to the value of the measurement point record to be processed.

[0043] For scenarios involving the addition of new measurement points at the site, when a new measurement point is first uploaded to the central control side along with a mutation data packet or a general call data packet, since there is no cached record for that measurement point in the full measurement point cache table, the comparison process will automatically create a new cached record for it, mark the value of that measurement point as pending persistence, immediately push it to the monitoring interface, and push it to the data processing program that subscribes to that measurement point type, thus achieving full-link automatic adaptation for the new measurement point. Similarly, when the site equipment is replaced or the measurement point is reconfigured, the new measurement point values ​​subsequently uploaded will overwrite the old values ​​in the cached record, automatically completing the data correction. For example, the measurement point records to be processed are shown in Table 1.

[0044] Table 1

[0045] In some embodiments, in step S203, a linkage operation is performed synchronously based on the same comparison result.

[0046] Specifically, the comparison results include two scenarios: the value changes (different) and the value does not change (same).

[0047] Scenario 1: The value of the measurement point to be processed is different from the value of the cached record (the value has changed).

[0048] In this case, based on the same comparison result, the following four linked operations are executed simultaneously: Operation ① Cache Update: Update the latest value of the cached record to the value of the measurement point record to be processed, update the first update time of the cached record to the acquisition time corresponding to the value of the measurement point record to be processed (indicating that the value changed at this moment), and update the last update time of the cached record to the acquisition time corresponding to the value of the measurement point record to be processed.

[0049] Operation ② Interface Push: The updated measurement point value is pushed to the monitoring interface subscribed to that measurement point on the centralized control side in real time. After receiving the push, the monitoring interface directly refreshes the display value of the corresponding measurement point. Since the push is completed in memory, it does not go through the I / O path of the time series database, and the latency can be controlled in the microsecond to millisecond range.

[0050] Operation ③ Persistence Marking: Mark the measurement point record to be processed as a state to be persisted (for example, set the persistence flag to true) and add it to the persistence write queue.

[0051] Operation ④ Program Push: The updated measurement point value is pushed to the data processing program subscribed to that measurement point. Specifically, the type of the measurement point (e.g., telemetry, remote signaling) and its unique identifier can be determined. Based on the pre-configured subscription relationship between the type and the data processing program, and the subscription relationship between the unique identifier of the measurement point and the data processing program, the updated measurement point value is pushed to the data processing programs subscribed to that type and those subscribed to that measurement point, respectively. The data processing program may include, but is not limited to, alarm centers, reporting programs, real-time calculation programs, and fault analysis programs.

[0052] It should be noted that although both operations ② and ④ involve pushing data, their targets differ: Operation ② targets the monitoring interface and is a point-to-point push, where a change in a single measurement point value is pushed to the monitoring interface subscribed to that measurement point; Operation ④ targets the subscribed data processing program and is a two-level targeted push based on the subscription relationship. The subscription is based on the measurement point's unique identifier and related attributes (attributes after segmenting and parsing the unique identifier, such as a system or component). Both operations are triggered by the same comparison result and execute in parallel at the memory level without blocking each other.

[0053] Scenario 2: The value of the measurement point to be processed is the same as the value of the cached record (the value has not changed).

[0054] In this scenario, only the last update time of the cached record is updated (updating the last update time to the current time). No interface push is performed, no marking for persistence is done, and no data is pushed to the data processing program. In other words, measurement point data whose values ​​have not changed are processed only after being compared and confirmed, and do not flow into any subsequent stages. For example, the cached record format in the full measurement point cache table is shown in Table 2.

[0055] Table 2

[0056] In some embodiments, when the time elapsed between the last update of a cached record at a measurement point and the most recent change (i.e., the first update) exceeds a first preset time, the value of the cached record corresponding to that measurement point will be marked as pending persistence, even without any new changes triggering the update, and the current value of that measurement point will be pushed to the monitoring interface. The first preset time can be configured according to on-site requirements, for example, set to 5 minutes or 10 minutes. This mechanism ensures that the data on the monitoring interface remains up-to-date even when there are no changes for a long period of time, and that the time-series database also retains periodic data anchors, avoiding "data gaps".

[0057] In some embodiments, if a measurement point fails to update after a second preset timeout period following its last update, a data acquisition anomaly message is generated and pushed to the monitoring interface. The second preset timeout period is longer than the cycle length for the central control side to issue a general call command to the field station side. For example, if the general call cycle is set to 3 minutes, the second preset timeout period can be set to 6 minutes (twice the general call cycle). This mechanism indicates that the measurement point may have experienced a data acquisition interruption or communication failure, reminding maintenance personnel to pay attention. It should be emphasized that the timeout detection in this disclosure is deployed on the central control master station side, based on the timestamps of the full measurement point cache table. It can perform centralized and unified monitoring of the timeout status of all measurement points in all subordinate field stations, which is different from the existing technology that disperses timeout judgments on field station gateways or terminal devices.

[0058] In some embodiments, in step S204, the measurement point records marked as pending persistence are written to the time series database. Specifically, the measurement point records marked as pending persistence can be placed in a write queue, and the measurement point records in the write queue are written to the time series database in batches according to a preset batch write cycle (e.g., 200 milliseconds to 500 milliseconds, which can be flexibly configured according to the write performance of the field time series database). Batch writing can effectively reduce the connection overhead and single transaction overhead of the time series database, and significantly improve the write throughput compared to the write-by-write method.

[0059] In some optional embodiments, a change threshold judgment mechanism can be introduced in the comparison step between the measurement point record to be processed and the cached record to filter out minor fluctuations in the measurement point data. Specifically, the amount of change between the value of the measurement point record to be processed and the latest value of the cached record is calculated; when the absolute value of the change is less than a preset fluctuation threshold (e.g., 0.1% of the telemetry engineering value range), the change is judged as invalid fluctuation and treated as "no change in value", that is, only the last update time is updated without performing interface push, persistent tagging, and program push. This mechanism can effectively avoid frequent invalid pushes and writes caused by sensor noise or signal fluctuations, further improving the data quality and resource utilization efficiency of the system.

[0060] In some optional embodiments, when communication between the field station and the central control station is interrupted and then restored, the field station typically sends a general call data packet to synchronize the latest status of all measurement points. The central control station processes this general call data packet using the same comparison and linkage process disclosed herein: for measurement points that changed during the communication interruption, the full measurement point cache table finds different values ​​after comparison, automatically triggers end-to-end push and persistent marking, and stores the new values ​​in the database; for measurement points that did not change during the interruption, only the last update time is refreshed. This mechanism can automatically correct data deviations that may occur during the disconnection, achieving rapid status synchronization after communication is restored.

[0061] Figure 3 This is a block diagram of a centralized control data management device based on cache comparison linkage, according to an embodiment of the present disclosure.

[0062] like Figure 3 As shown, the device is located on the central control side and includes: The cache maintenance unit 410 is configured to maintain a full measurement point cache table that corresponds one-to-one with the measurement points at the station on the central control side. The full measurement point cache table resides in the memory of the central control side and is used to store the latest value and update time of each measurement point.

[0063] The parsing and comparison unit 420 is configured to receive and parse the mutation data packets and general call data packets uploaded by the site side, generate the test point records to be processed, and compare the test point records to be processed with the corresponding cache records in the full test point cache table.

[0064] The linkage execution unit 430 is configured to perform the following operations synchronously based on the same comparison result: when the value of the measurement point record to be processed is different from the value of the cache record, the value of the cache record is updated to the value of the measurement point record to be processed, and the last update time of the cache record is updated. At the same time, the updated measurement point value is pushed to the monitoring interface on the centralized control side in real time, the measurement point record to be processed is marked as pending persistence, and the updated measurement point value is pushed to the data processing program that subscribes to the measurement point; when the value of the measurement point record to be processed is the same as the value of the cache record, only the last update time of the cache record is updated.

[0065] The persistence unit 440 is configured to write measurement point records marked as pending persistence status into the time series database.

[0066] Figure 4 This is a schematic block diagram illustrating an electronic device according to an embodiment of the present disclosure. (Refer to...) Figure 4 The electronic device 500 may include one or more of the following components: processing component 502, memory 504, power supply component 506, multimedia component 508, audio component 510, input / output (I / O) interface 512, sensor component 514, and communication component 516.

[0067] Processing component 502 typically controls the overall operation of electronic device 500, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 502 may include one or more processors 520 to execute instructions to complete all or part of the steps of the data management method described above. Furthermore, processing component 502 may include one or more modules to facilitate interaction between processing component 502 and other components. For example, processing component 502 may include a multimedia module to facilitate interaction between multimedia component 508 and processing component 502.

[0068] Memory 504 is configured to store various types of data to support the operation of electronic device 500. Examples of such data include instructions for any application or method operating on electronic device 500, contact data, phonebook data, messages, pictures, videos, etc. Memory 504 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0069] Power supply component 506 provides power to various components of electronic device 500. Power supply component 506 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 500.

[0070] Multimedia component 508 includes a screen that provides an output interface between electronic device 500 and user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 508 includes a front-facing camera and / or a rear-facing camera. When electronic device 500 is in an operating mode, such as a shooting mode or video mode, the front-facing camera and / or rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0071] Audio component 510 is configured to output and / or input audio signals. For example, audio component 510 includes a microphone (MIC) configured to receive external audio signals when electronic device 500 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 504 or transmitted via communication component 516. In some embodiments, audio component 510 also includes a speaker for outputting audio signals.

[0072] I / O interface 512 provides an interface between processing component 502 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, start buttons, and lock buttons.

[0073] Sensor assembly 514 includes one or more sensors for providing state assessments of various aspects of electronic device 500. For example, sensor assembly 514 may detect the on / off state of electronic device 500, the relative positioning of components such as the display and keypad of electronic device 500, changes in position of electronic device 500 or a component of electronic device 500, the presence or absence of user contact with electronic device 500, orientation or acceleration / deceleration of electronic device 500, and temperature changes of electronic device 500. Sensor assembly 514 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 514 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 514 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0074] Communication component 516 is configured to facilitate wired or wireless communication between electronic device 500 and other devices. Electronic device 500 can access wireless networks based on communication standards, such as WiFi, 2G, 3G, 4G LTE, 5G NR, or combinations thereof. In one exemplary embodiment, communication component 516 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 516 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0075] In an exemplary embodiment, the electronic device 500 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the data management method described above.

[0076] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 504 including instructions, which can be executed by a processor 520 of an electronic device 500 to complete the data management method described above. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0077] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the disclosure herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0078] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

[0079] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0080] The methods and apparatus provided in the embodiments of this disclosure have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this disclosure. The descriptions of the embodiments above are only for the purpose of helping to understand the methods and core ideas of this disclosure. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this disclosure. Therefore, the content of this specification should not be construed as a limitation of this disclosure.

Claims

1. A centralized control data management method based on cache comparison and linkage, characterized in that, Applied to the centralized control side, the method includes: A full measurement point cache table is maintained on the central control side, corresponding one-to-one with each measurement point on the field station side. The full measurement point cache table resides in the memory of the central control side and is used to store the latest value and update time of each measurement point. Receive and parse the mutation data packets and general call data packets uploaded by the site side to generate the measurement point records to be processed; The record of the measurement point to be processed is compared with the corresponding cache record in the full measurement point cache table; Based on the same comparison result, the following linkage operations are executed synchronously: when the value of the measurement point record to be processed is different from the value of the cache record, the value of the cache record is updated to the value of the measurement point record to be processed, and the first update time and the last update time of the cache record are updated. At the same time, the updated measurement point value is pushed to the monitoring interface on the centralized control side in real time, the measurement point record to be processed is marked as pending persistence, and the updated measurement point value is pushed to the data processing program that subscribes to the measurement point. When the value of the measurement point record to be processed is the same as the value of the cache record, only the last update time of the cache record is updated; Write the measurement point records marked as pending persistence to the time series database.

2. The method according to claim 1, characterized in that, Based on the same comparison result, the following linked operations are also performed synchronously: When the latest value of a measurement point's cached record is more than a first preset time interval since the last change, the value of the cached record corresponding to that measurement point is marked as pending persistence, and the current value of that measurement point is pushed to the monitoring interface.

3. The method according to claim 1, characterized in that, The mutation data packet is actively uploaded by the field station when the collected measurement point value changes abruptly; the general call data packet is uploaded by the field station after receiving the general call command issued by the central control side, which packages the latest values ​​of all measurement points.

4. The method according to claim 1, characterized in that, The full measurement point cache table is constructed by loading the latest value of each measurement point at the last timestamp from the time series database during initial startup. After construction, it resides in the memory of the central control side and serves as the comparison benchmark and push hub for all subsequent data processing.

5. The method according to claim 1, characterized in that, The step of comparing the record of the measurement point to be processed with the corresponding cache record in the full measurement point cache table includes: Based on the measurement point identifier of the measurement point record to be processed, search for a cache record with the same identifier in the full measurement point cache table; The value of the measurement point to be processed is compared with the value of the cached record found.

6. The method according to claim 1, characterized in that, The step of writing the measurement point records marked as pending persistence into the time series database includes: Place the measurement point records marked as pending persistence into the write queue; According to the preset batch write cycle, the measurement point records in the write queue are written to the time series database in batches.

7. The method according to claim 1, characterized in that, The step of pushing the updated measurement point value to the data processing program that subscribes to the measurement point includes: Determine the type of the measuring point and its unique identifier; Based on the pre-configured subscription relationship between the type and the data processing program, and the subscription relationship between the unique identifier of the measurement point and the data processing program, the updated measurement point value is pushed to the data processing program that subscribes to the type and the data processing program that subscribes to the measurement point, respectively. The data processing program includes at least one of an alarm center, a reporting program, a real-time calculation program, and a fault analysis program.

8. The method according to claim 1, characterized in that, The method further includes: When the last update time of a measurement point exceeds the second preset time without being updated, a data acquisition anomaly prompt message is generated and pushed to the monitoring interface; wherein, the second preset time is longer than the cycle time for the central control side to issue a general call command to the field station side.

9. A centralized control data management device based on cache comparison linkage, characterized in that, Located on the central control side, the device includes: The cache maintenance unit is configured to maintain a full measurement point cache table on the central control side that corresponds one-to-one with each measurement point on the field station side. The full measurement point cache table resides in the memory of the central control side and is used to store the latest value and update time of each measurement point. The parsing and comparison unit is configured to receive and parse the mutation data packets and general call data packets uploaded by the site side, generate a test point record to be processed, and compare the test point record to be processed with the corresponding cache record in the full test point cache table; The linkage execution unit is configured to synchronously perform the following operations based on the same comparison result: when the value of the measurement point record to be processed is different from the value of the cache record, update the value of the cache record to the value of the measurement point record to be processed, and update the first update time and the last update time of the cache record. At the same time, push the updated measurement point value to the monitoring interface on the centralized control side in real time, mark the measurement point record to be processed as pending persistence, and push the updated measurement point value to the data processing program that subscribes to the measurement point; when the value of the measurement point record to be processed is the same as the value of the cache record, only update the last update time of the cache record. The persistence unit is configured to write measurement point records marked as pending persistence status to the time series database.

10. An electronic device, characterized in that, include: Processor, memory; The memory is used to store computer programs; The processor is configured to execute the method as described in any one of claims 1-8 by invoking the computer program.

Images