A method for optimizing reporting and supplementary reporting by intelligent fusion terminals, the terminal and the medium

Abstract

This invention relates to the field of terminal data transmission technology, specifically providing an optimization method, terminal, and medium for intelligent fusion terminal reporting and supplementary reporting. The method includes: polling pending reporting tasks, determining whether the reporting task is a range reporting task, and further determining whether it is a low-frequency reporting task; if so, generating a corresponding supplementary reporting task based on the reporting task, modifying the execution cycle of the pending reporting task and the supplementary reporting task to achieve same-day supplementary reporting for low-frequency reporting tasks; if the reporting task is not a low-frequency reporting task, determining whether the end time of the data selection range of the reporting task is later than the task execution time; if so, compensating the execution cycle of the data selection range; executing the data reporting of the reporting task; if a supplementary reporting task has already been generated, executing the data reporting of the supplementary reporting task simultaneously. Correction is performed when the end time of the data selection range of the reporting task is later than the current execution time, avoiding future time issues and ensuring the integrity of the reported collected data.

Description

Technical Field

[0001] This invention belongs to the field of terminal data transmission technology, and particularly relates to an intelligent fusion terminal reporting and supplementary reporting optimization method, terminal and medium. Background Technology

[0002] Data acquisition and reporting are the most basic and critical functions of a fusion terminal. In power information acquisition systems, the timeliness and completeness of data reporting are two core indicators for measuring terminal acquisition performance and meeting assessment standards. However, in practical applications, these two indicators are often difficult to achieve simultaneously within the existing technological framework. Specifically, if the data collected in the previous cycle is reported in the current cycle, data completeness can be guaranteed, but real-time reporting is poor; if the data collected in the current cycle is reported in the current cycle, the real-time requirement is met, but if there is a time point later than the current time when selecting the reporting interval, the interval reporting will have a "future time" problem, leading to data reporting failure.

[0003] To meet the performance requirements for data acquisition completeness of fusion terminals and to mitigate data loss due to external interference, existing terminals are generally equipped with supplementary data collection and reporting tasks. Currently, the mainstream approach to supplementary data collection tasks is to derive a corresponding supplementary task from the original acquisition task issued by the host computer, used to supplement the collection of frozen data within the historical period. If the supplementary data collection task fails on the first attempt, the system can repeat the task multiple times until data points for all measurement points have been collected.

[0004] However, for supplementary data collected using the 96-point curve scheme, it can be reported together in the next reporting cycle, which has no significant impact on real-time performance. But for low-frequency collection schemes such as daily freezing, only one reporting task is performed per day, resulting in significant differences in supplementary reporting and a substantial reduction in real-time performance. To address this issue, some existing technologies use a transparent transmission reporting method, where the downlink module directly transmits the data to the uplink module and reports it to the main station after collection, achieving immediate reporting upon collection. However, this method leads to the same data point being packaged and reported again in the regular reporting task of the next cycle, resulting in duplicate reporting. Other technologies use a marking reporting method, where the terminal periodically checks the timestamps of the daily frozen data collected in the data center, filtering and packaging data later than the last reporting time for reporting. However, this method requires the terminal to frequently access the data center for checks, significantly impacting the overall operating efficiency of the terminal. Summary of the Invention

[0005] To address the problems existing in the prior art, the present invention provides an optimization method for intelligent fusion terminal reporting and supplementary reporting, comprising the following steps: Step S1: Poll the reporting tasks to be executed, determine whether the reporting task is an interval reporting task, and further determine whether it is a low-frequency reporting task. Step S2: If it is a low-frequency reporting task, a corresponding supplementary reporting task is generated based on the reporting task. The execution cycle of the reporting task to be executed and the supplementary reporting task is modified to realize the same-day supplementary reporting of the low-frequency reporting task. Then, proceed to step S5. Step S3: If the reporting task is not a low-frequency reporting task, determine whether the end time of the data selection interval of the reporting task is later than the task execution time. Step S4: If so, perform period compensation on the selected data interval to correct the end time and start time; Specifically, the period compensation in step S4 is as follows: S41: Calculate the time difference T between the end time and the task execution time. c = T exec - T end , among which, T exec For the time of task execution, T end The end time; S42: Correct the end time to the task execution time: T' end = T exec , where T' end This is the corrected end time; S43: Correct the start time based on the time difference: T' start = T start - T c , where T' start The corrected start time; Step S5: Perform the data reporting of the reporting task; if a supplementary reporting task has been generated, perform the data reporting of the supplementary reporting task at the same time.

[0006] Furthermore, step S2 includes setting the original reporting task for generating the supplementary reporting task: Set the start time of the data selection interval for the original reporting task to 00:00 of the current day, and the end time to the task execution time.

[0007] Based on the above scheme, step S2 further includes: S21: Based on the original reporting task, set the reporting method and task execution frequency of the supplementary reporting task; S22: Modify the reporting method of the supplementary reporting task to an interval reporting method based on the successful data collection time, and set the task delay to 0.

[0008] Specifically, the period modification in step S2 includes: Step S23: Determine whether the execution time of the supplementary reporting task is less than the execution time of the original reporting task; S24: If yes, the supplementary reporting task will not be executed in this round of tasks; if no, determine whether this round of supplementary reporting is the first supplementary reporting after the original reporting task has been executed. S25: If this is the first time a supplementary report is submitted, the start time of the data selection interval for the supplementary report task will be changed to the end time of the original reporting task.

[0009] Preferably, the periodic compensation is also applied to non-low-frequency interval reporting tasks, including daily freeze, minute freeze, and monthly freeze reporting schemes; the end time of the interval reporting task is compared with the task execution time, and if the end time is later than the task execution time, the periodic compensation is performed.

[0010] On the other hand, the present invention provides an intelligent fusion terminal, comprising: The first judgment module is used to poll the reporting tasks to be executed, determine whether the current reporting task is an interval reporting task, and further determine whether it is a low-frequency reporting task. If the supplementary reporting generation module is a low-frequency reporting task, it generates a corresponding supplementary reporting task based on the reporting task, modifies the execution cycle of the reporting task to be executed and the supplementary reporting task to achieve same-day supplementary reporting for low-frequency reporting tasks, and then jumps to the data reporting module. The second judgment module, if the reporting task is not a low-frequency reporting task, is used to determine whether the end time of the data selection interval of the reporting task is later than the task execution time. If so, the periodic compensation module performs periodic compensation on the selected data interval to correct the end time and start time. The periodic compensation module specifically includes: The calculation unit is used to calculate the time difference T between the end time and the task execution time. c = T exec - T end , among which, T exec T is the execution time of the terminal task. end The end time; The first correction unit is used to correct the end time, setting the end time equal to the task execution time: T' end =T exec , where T' end This is the corrected end time; The second correction unit is used to correct the start time T' based on the time difference. start = T start - T c , where T' start The corrected start time; The data reporting module performs data reporting tasks; if a supplementary reporting task has been generated, it also performs the data reporting for the supplementary reporting task.

[0011] The present invention also provides a computer-readable storage medium having a computer program, which, when executed by a processor, implements the steps of the intelligent fusion terminal reporting and supplementary reporting optimization method described above.

[0012] Compared with the prior art, the present invention has the following beneficial effects: When the end time of the data selection interval for the reporting task is later than the current execution time, the end time is corrected to the current time, and the start time is compensated in reverse to keep the interval length unchanged; this avoids the "future time" problem, which not only meets the real-time requirements of the current cycle but also ensures the complete reporting of the collected data; For low-frequency reporting tasks such as daily freezing, supplementary reporting tasks with higher execution frequency are derived, and an interval reporting method based on the successful data collection time is adopted. This ensures that data collected later than the original task execution time can be promptly sent through subsequent supplementary reporting tasks. At the same time, the execution time comparison is used to prevent supplementary reporting tasks from executing earlier than the original task, thus avoiding duplicate data reporting. The start time of the data selection interval for the first supplementary reporting task after the original task is executed is set to the end time of the original task, so that the data interval of the task can fully cover 24 hours, achieving seamless coverage of the time range and greatly improving the data collection completeness rate. By achieving supplementary reporting through task-level derivation and scheduling, there is no need to periodically scan the data center for timestamp comparison, which significantly reduces the frequent access to the data center and CPU resources, reduces the terminal operating load, and ensures the long-term stable operation of the equipment. Periodic compensation can be applied to daily freeze, minute freeze, and monthly freeze schemes to compensate for and optimize task configuration defects. It has good scalability and versatility, eliminating the need for repeated development for different data acquisition schemes and reducing maintenance costs. Attached Figure Description

[0013] Figure 1 This is a flowchart of the optimization method of the present invention; Figure 2 This is a flowchart of the low-frequency task supplementary reporting method for this application; Figure 3 This is a flowchart of the periodic compensation method for this application. Detailed Implementation

[0014] First, the basic concepts underlying this invention will be introduced to facilitate understanding of the invention, as follows: This invention is based on the reporting method defined in the "Object-Oriented Electricity Consumption Information Data Exchange Protocol", wherein: Method 6 is selected as the interval reporting method based on the collection start time. The data selection interval is defined by the start value and end value of the collection start time. Method 7 is selected as the interval reporting method based on the collection and storage time. The data selection interval is defined by the start value and end value of the collection and storage time. Method 8 is selected as the interval reporting method based on the successful collection time. The data selection interval is defined by the start value and end value of the successful collection time.

[0015] The above selection methods 6-8 are interval reporting, where data within the specified interval will be selected for reporting.

[0016] This invention addresses the task of reporting data between intervals. The invention will be further described below with reference to specific embodiments.

[0017] like Figure 1 and Figure 2 As shown, this invention provides an optimization method for intelligent fusion terminal reporting and supplementary reporting, comprising the following steps: Step S1: Poll the reporting tasks to be executed, determine whether the current reporting task is an interval reporting task, and further determine whether it is a low-frequency reporting task. In this embodiment, low-frequency reporting tasks refer to daily, monthly, and yearly freeze tasks with long reporting cycles. Specifically, when a low-frequency reporting task is detected, the relevant parameters of the original reporting task are replicated to generate a supplementary reporting task corresponding to the original reporting task.

[0018] Furthermore, the terminal obtains an idle task ID from the currently idle task identifier pool and assigns it to the supplementary reporting task.

[0019] Step S2: If it is a low-frequency reporting task, generate a corresponding supplementary reporting task based on the reporting task, modify the execution cycle of the reporting task to be executed and the supplementary reporting task to achieve same-day supplementary reporting for low-frequency reporting tasks, and then jump to step S5. Specifically, step S2 also includes: Determine whether it is a supplementary reporting task to be executed. If not, further determine whether it is an original reporting task with a supplementary reporting task. If so, process the original reporting task by setting it to an interval reporting method based on the successful data collection time (select method 8), and set the start time of its data selection interval to 00:00 of the current day, with the data selection interval being from 00:00 of the current day to the task execution time.

[0020] This step further includes configuring the generated supplementary reporting task: S21: Based on the original reporting task, set the reporting method and task execution frequency for the supplementary reporting task; S22: Modify the reporting method of the supplementary reporting task to an interval reporting method based on the successful data collection time, and set the task delay to 0. Set the supplementary reporting task to be executed on the hour, and set the task execution frequency to once per hour.

[0021] This interval reporting method ensures successful data collection and aligns with the logic of collecting data in the current cycle and reporting it in the next. It's important to note that since method 8 is based on the successful data collection time, it can distinguish the time of data collection. For example, if 100 meters need data collected at 00:00 on a certain day, in actual collection, data from 70 meters is collected during real-time task execution, while data from the other 30 meters is collected through supplementary readings. Accurate supplementary reporting based on the supplementary reading data requires distinguishing between these two data points using method 8.

[0022] The above configuration ensures that the supplementary reporting task is executed on the hour and at midnight, and reports the previous cycle's task.

[0023] Furthermore, to prevent duplicate reporting, step S2 includes: S23: Determine whether the execution time of the supplementary reporting task is earlier than the execution time of the original reporting task; When the task execution time is reached, the next execution time is calculated while the execution data is being selected and reported. This process is repeated until the next execution time is reached, and the results are compared before each execution.

[0024] S24: If the time is earlier than the original reporting task execution time, the supplementary reporting task will not be executed in this round of tasks; if the time is later than the original reporting task execution time, the next execution time will be calculated. Further determination is needed to determine whether this round of supplementary reporting is the first supplementary reporting after the original reporting task was completed; Preferably, except at 0:00, if the execution time of the supplementary reporting task is earlier than that of the original reporting task, data reporting will not be initiated to ensure that data already reported in the original task will not be reported repeatedly in the supplementary reporting task. In order to ensure that data collected between 23:00 and 24:00 can also be reported, special handling is applied to 0:00. Although 0:00 is earlier than the execution time of the original reporting task, data reporting needs to be initiated at this time.

[0025] S25: If this is the first time a supplementary report is submitted, the start time of the data selection interval for the supplementary report task will be changed to the end time of the data selection interval for the original report task.

[0026] Step S25 modifies the data selection range of the first supplementary reporting task, so that the ranges of the original task and all supplementary reporting tasks are connected end to end on the timeline, achieving complete coverage of 24 hours a day without overlap, ensuring that all collected data can be reported in a timely and accurate manner.

[0027] In existing technologies, to ensure the real-time nature of reported data, data for the current period must be reported. After the task begins execution, data collection is performed between 15:45:00 and 16:00:00. Normally, data collection can be completed between 15:45:00 and 15:49:00. However, when network fluctuations cause meter reading failures, data collection may not be completed until 15:59:00. By this time, the reporting task has already been completed, resulting in data reporting failure. Therefore, for interval reporting, the data to be reported at 15:55:00 should be within the interval of 15:45:00 to 16:00:00. This presents a future timeframe where data collection may be completed at 15:59:00, which this paper refers to as the "future time" problem.

[0028] To address the "future moment" problem, the present invention further includes: Step S3: If the reporting task is not a low-frequency reporting task, determine whether the end time of the data selection interval of the reporting task is later than the task execution time. Step S4: If so, perform periodic compensation on the selected data interval to correct the end time and start time.

[0029] According to a preferred embodiment, such as Figure 3 As shown, the period compensation in step S4 is as follows: S41: Calculate the time difference T between the end time and the task execution time. c = T exec - T end , among which, T exec T is the execution time of the terminal task. end The end time; S42: Modify the end time, changing the end time to the task execution time: T' end = T exec , where T' end This is the corrected end time; S43: Adjust the start time based on the time difference: T' start = T start - T c , where T' start This is the corrected start time.

[0030] Through the above-described periodic compensation steps, reverse compensation is achieved for data exceeding the time limit. Under the condition that the current period is reported and the interval length remains unchanged, a complete report of the current period is achieved, so as to solve the data reporting failure caused by future time issues.

[0031] Preferably, the periodic compensation is also applied to interval reporting tasks, including reporting schemes such as minute freeze, daily freeze, and monthly freeze; by comparing the end time of the interval reporting task with the task execution time, if the end time is later than the task execution time, the periodic compensation step is executed.

[0032] According to a comparative implementation method, to solve the data loss problem caused by task reporting failures, a direct adjustment is to change the original low-frequency reporting task to a higher-frequency task. For example, changing the original task of reporting once a day to reporting 24 times a day, in order to reduce the impact of single data loss by increasing the sampling density. However, this method has the following drawbacks: First, the initial reporting time after modification often fails to align with the user's actual configured task execution time, causing the timestamp of the reported data to deviate from expectations and affecting data consistency and availability. Second, to implement data integrity verification and missing data reporting, an additional statistics thread needs to be established to continuously mark and filter reported and unreported data, and to re-select data from the unreported tasks when supplementary reporting is needed. This processing mechanism is logically complex, not only increasing the difficulty of software implementation but also significantly consuming terminal computing and storage resources, thus reducing system operating efficiency.

[0033] Step S5: Perform the data reporting of the reporting task; if a supplementary reporting task has been generated, perform the data reporting of the supplementary reporting task at the same time.

[0034] Specifically, the terminal retrieves the corresponding frozen data from the data center according to the corrected data selection range and uploads it to the main station.

[0035] Based on the same technical concept, the present invention also provides a converged terminal, comprising: The first judgment module is used to poll the reporting tasks to be executed, determine whether the current reporting task is an interval reporting task, and further determine whether it is a low-frequency reporting task. If the supplementary reporting generation module is a low-frequency reporting task, it generates a corresponding supplementary reporting task based on the reporting task, modifies the execution cycle of the reporting task to be executed and the supplementary reporting task to achieve same-day supplementary reporting for low-frequency reporting tasks, and then jumps to the data reporting module. The second judgment module, if the reporting task is not a low-frequency reporting task, is used to determine whether the end time of the data selection interval of the reporting task is later than the task execution time. If so, the periodic compensation module performs periodic compensation on the selected data interval to correct the end time and start time. The data reporting module performs data reporting tasks; if a supplementary reporting task has been generated, it also performs the data reporting for the supplementary reporting task.

[0036] The periodic compensation module specifically includes: The calculation unit is used to calculate the time difference T between the end time and the task execution time. c = T exec - T end , among which, T exec T is the execution time of the terminal task. end The end time; The first correction unit is used to correct the end time, setting the end time equal to the task execution time: T' end = T exec , where T' end This is the corrected end time; The second correction unit is used to correct the start time based on the time difference: T' start = T start - T c , where T' start This is the corrected start time.

[0037] Furthermore, the intelligent fusion terminal reporting and supplementary reporting optimization method according to the present invention can be recorded in a computer-readable recording medium. Specifically, according to the present invention, a computer-readable recording medium storing computer-executable instructions can be provided, which, when executed by a processor, can cause the processor to execute the intelligent fusion terminal reporting and supplementary reporting optimization method as described above.

[0038] It should be noted that the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or portion of code containing at least one executable instruction for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0039] In general, various exemplary embodiments of the present invention can be implemented in hardware or dedicated circuitry, software, firmware, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. When aspects of embodiments of the present invention are illustrated or described as block diagrams, flowcharts, or represented using certain other images, it will be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented as non-limiting examples in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or certain combinations thereof.

[0040] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

[0041] While the specific embodiments of the present invention have been described above, they are not intended to limit the scope of protection of the present invention. Those skilled in the art should understand that various modifications or variations that can be made by those skilled in the art without creative effort based on the technical solutions of the present invention are still within the scope of protection of the present invention.

Claims

1. A method for optimizing reporting and supplementary reporting by intelligent fusion terminals, characterized in that, Includes the following steps: Step S1: Poll the reporting tasks to be executed, determine whether the reporting task is an interval reporting task, and further determine whether it is a low-frequency reporting task. Step S2: If it is a low-frequency reporting task, a corresponding supplementary reporting task is generated based on the reporting task. The execution cycle of the reporting task to be executed and the supplementary reporting task is modified to realize the same-day supplementary reporting of the low-frequency reporting task. Then, proceed to step S5. Step S3: If the reporting task is not a low-frequency reporting task, determine whether the end time of the data selection interval of the reporting task is later than the task execution time. Step S4: If so, perform period compensation on the selected data interval to correct the end time and start time; Specifically, the periodic compensation is as follows: S41: Calculate the time difference T between the end time and the task execution time. c = T exec - T end , among which, T exec For the time of task execution, T end The end time; S42: Correct the end time to the task execution time: T' end = T exec , where T' end This is the corrected end time; S43: Correct the start time based on the time difference: T' start = T start - T c , where T' start The corrected start time; Step S5: Perform the data reporting of the reporting task; if a supplementary reporting task has been generated, perform the data reporting of the supplementary reporting task at the same time.

2. The intelligent fusion terminal reporting and supplementary reporting optimization method according to claim 1, characterized in that, Step S2 includes setting the original reporting task for generating the supplementary reporting task: Set the start time of the data selection interval for the original reporting task to 00:00 of the current day, and the end time to the task execution time.

3. The intelligent fusion terminal reporting and supplementary reporting optimization method according to claim 2, characterized in that, Step S2 further includes: S21: Based on the original reporting task, set the reporting method and task execution frequency of the supplementary reporting task; S22: Modify the reporting method of the supplementary reporting task to an interval reporting method based on the successful data collection time, and set the task delay to 0.

4. The intelligent fusion terminal reporting and supplementary reporting optimization method according to claim 1, characterized in that, The periodic modification in step S2 includes: Step S23: Determine whether the execution time of the supplementary reporting task is less than the execution time of the original reporting task; S24: If yes, the supplementary reporting task will not be executed in this round of tasks; if no, determine whether this round of supplementary reporting is the first supplementary reporting after the original reporting task has been executed. S25: If this is the first time a supplementary report is submitted, the start time of the data selection interval for the supplementary report task will be changed to the end time of the original reporting task.

5. The intelligent fusion terminal reporting and supplementary reporting optimization method according to claim 1, characterized in that, The periodic compensation is also applied to non-low-frequency interval reporting tasks, including daily freeze, minute freeze, and monthly freeze reporting schemes; the end time of the interval reporting task is compared with the task execution time, and if the end time is later than the task execution time, the periodic compensation is performed.

6. A smart converged terminal, characterized in that, include: The first judgment module is used to poll the reporting tasks to be executed, determine whether the current reporting task is an interval reporting task, and further determine whether it is a low-frequency reporting task. If the supplementary reporting generation module is a low-frequency reporting task, it generates a corresponding supplementary reporting task based on the reporting task, modifies the execution cycle of the reporting task to be executed and the supplementary reporting task to achieve same-day supplementary reporting for low-frequency reporting tasks, and then jumps to the data reporting module. The second judgment module, if the reporting task is not a low-frequency reporting task, is used to determine whether the end time of the data selection interval of the reporting task is later than the task execution time. If so, the periodic compensation module performs periodic compensation on the selected data interval to correct the end time and start time. The periodic compensation module specifically includes: The calculation unit is used to calculate the time difference T between the end time and the task execution time. c = T exec - T end , among which, T exec T is the execution time of the terminal task. end The end time; The first correction unit is used to correct the end time to the task execution time: T' end = T exec , where T' end This is the corrected end time; The second correction unit is used to correct the start time T' based on the time difference. start = T start - T c , where T' start The corrected start time; The data reporting module performs data reporting tasks; if a supplementary reporting task has been generated, it also performs the data reporting for the supplementary reporting task.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium has a computer program, which, when executed by a processor, implements the intelligent fusion terminal reporting and supplementary reporting optimization method as described in any one of claims 1-5.

Images