A method, system, and medium for supplementing missing data reports in integrated terminal data reporting

Abstract

This invention relates to the field of converged terminal technology, specifically providing a method, system, and medium for supplementing missing data reporting from converged terminals. The method employs a reporting task initialization mechanism that clears historical data and re-initializes the system when the converged terminal powers on or when the task plan or table file changes. It utilizes a collection plan matching strategy based on matching degree and recall interval to accurately select the target collection plan. A two-level supplementary reporting mechanism is combined: self-supplementary reporting and failed list supplementary reporting. In the self-supplementary reporting stage, supplementary reporting is scheduled according to the protocol timeout period; in the failed list stage, periodic supplementary reporting, forced supplementary reporting, and redundant data cleanup are performed. Through these steps, the completeness and reliability of converged terminal data reporting are effectively improved, ensuring the accuracy of the main station's statistics on collection success rate.

Description

Technical Field

[0001] This invention belongs to the field of converged terminal technology, and in particular relates to a method, system and medium for supplementing missing data reporting in converged terminals. Background Technology

[0002] Data reporting is a core function of the converged terminal, and its stable operation directly affects the integrity and accuracy of electricity data collection. In normal operation, the converged terminal needs to match the appropriate execution rules from the meter reading scheme set by the main station, based on the pre-configured reporting tasks and corresponding reporting schemes. When the reporting task trigger time arrives, the converged terminal will extract the collected meter data and perform the data upload operation according to the reporting scheme bound to the task.

[0003] However, the complexity of the on-site operating environment often leads to data reporting anomalies. During meter reading and reporting, situations such as weak 4G signals, sudden network interruptions, malfunctions of the converged terminal itself, or power outages occur frequently. These anomalies can directly cause missing data reports, thereby affecting the accuracy of the main station's statistics on the success rate of converged terminal data collection.

[0004] To ensure the reliability of data reporting, the "Version 22 Data Acquisition Terminal Protocol Consistency Testing Specification" clearly stipulates that during the reporting process, the supplementary reporting mechanism must be executed according to the maximum number of times set in protocol field 601D, and the supplementary reporting timeout time also follows the configuration of this field. Taking curve data reporting as an example, the standard configuration is a timeout time of 1 minute and a maximum of 3 supplementary reporting attempts. However, in actual applications, there are still uncontrollable factors: if the master station experiences processing delays or malfunctions, it may be unable to respond to the three reporting messages from the converged terminal within 3 minutes; or due to poor communication link quality, the converged terminal may not receive a reply from the master station within the 3-minute supplementary reporting window. Both of these situations will lead to the failure of meter data reporting, ultimately reducing the data acquisition success rate of the converged terminal. Summary of the Invention

[0005] To address the problems existing in the prior art, the present invention provides a method for supplementing missing data reporting in a converged terminal, used in a converged terminal, comprising the following steps:

[0006] Step S1: When the system is powered on, a change in the task plan is detected, or a change in the table file is detected, the initialization of the reporting task is performed, and the reporting data in the database and linked list is cleared.

[0007] Step S2: Based on the reporting task and plan, traverse all ordinary data collection plans, select the matching plan, and report the collected data.

[0008] Step S3: Store the reported data in the database and create a scheduled task to send the data. If the scheduled task receives a reply from the master station after sending the data, delete the data in the database and delete the scheduled task to send the data. If no reply is received from the master station, perform a supplementary report for the scheduled task according to the protocol.

[0009] Step S4: If the number of supplementary reports for the scheduled task in step S3 exceeds the timeout number of the 601D reporting scheme, delete the scheduled task and put the supplementary report data into the failure list, and perform supplementary reporting for the failure list.

[0010] Based on the above scheme, the failure list replenishment in step S4 specifically includes the following steps:

[0011] S41: The data in the failure list follows the time period of the normal data report and waits for the normal data report to be completed within the time period;

[0012] S42: After the normal data reporting is completed, the data in the failure list is reported. Every T1 time, the data in the failure list is checked to see if it has been re-reported. If it has not been re-reported, it is forced to be re-reported once.

[0013] S43: Check if the number of times the data in the failure list has been reported exceeds N and whether the report was successfully reported within time T2. If it is unsuccessful, the data in the failure list is considered redundant and deleted from the failure list.

[0014] Further, step S2 includes:

[0015] S21: Determine if the current time matches the reporting time of the reporting task;

[0016] S22: Traverse the common collection schemes, and obtain the common collection scheme with the highest matching degree as the matching scheme by comparing the object attribute data in the common collection schemes.

[0017] Preferably, step S2 further includes:

[0018] S23: When there are multiple ordinary collection schemes with the same matching degree, the ordinary collection scheme shall be selected as the matching scheme based on whether the call interval with the reporting task is the same.

[0019] S24: If the recall intervals of the multiple common acquisition schemes are all different, the common acquisition scheme whose recall interval is a multiple of the reporting task recall interval is the matching scheme.

[0020] Based on the above scheme, if no reply is received from the main station in step S3, a timed task report is performed according to 601D. The interval of the timed task is the timeout period specified by 601D, and the number of reports is the number of reports of 601D.

[0021] Preferably, obtaining the matching scheme in step S22 specifically includes:

[0022] S221: Obtain the data item identifier of the reporting scheme and compare the data item identifier of the reporting scheme with the data item identifier of the ordinary collection scheme one by one;

[0023] S222: Select the common data collection scheme with the largest number of data item identifiers that are the same as the reported scheme as the matching scheme.

[0024] Based on the same inventive concept, the present invention provides a system for supplementing missing data reports in integrated terminal data reporting, comprising:

[0025] The initialization module is used to initialize the reporting task and clear the reporting data in the database and linked list when the system boots up, detects changes in the task plan, or detects changes in the table file.

[0026] The matching and reporting module is used to iterate through all ordinary data collection schemes based on the reporting task and scheme, and select the matching scheme to report the collected data.

[0027] The self-reporting module is used to store the reported data into the database and create a scheduled task to send the data. If the scheduled task receives a reply from the master station after sending the data, the data in the database is deleted and the scheduled task for sending the data is deleted. If no reply is received from the master station, the scheduled task is re-reported according to the protocol.

[0028] The failure list reporting module is used to delete the timed task and put the reporting data into the failure list when the number of reporting attempts of the timed task in the self-reporting module exceeds the protocol limit, and to perform failure list reporting.

[0029] Furthermore, the matching reporting module includes:

[0030] The first selection unit is used to traverse the common collection schemes and obtain the common collection scheme with the highest matching degree as the matching scheme by comparing the object attribute data in the common collection schemes.

[0031] The second selection unit is used to select the ordinary collection scheme with the same call interval as the reporting task as the matching scheme when there are multiple ordinary collection schemes with the same matching degree.

[0032] The third selection unit is used to select the ordinary acquisition scheme whose recall interval is a multiple of the reporting task recall interval as the matching scheme when the recall intervals of the multiple ordinary acquisition schemes are all different.

[0033] 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 method for supplementing missing data reporting in a fusion terminal as described above.

[0034] Compared with the prior art, the present invention has the following beneficial effects:

[0035] 1. In the event of an anomaly in the fusion terminal, the system automatically re-reports the daily frozen and curve data that were not successfully reported, ensuring the integrity of the daily frozen and curve data and improving the success rate of data collection by the main station's statistical fusion terminal;

[0036] 2. Based on the self-reporting mechanism, a failed linked list reporting mechanism is proposed. Without affecting the normal reporting task, the data that was not successfully reported can be stored in the database for 12 hours, thus maximizing the integrity of the reported data. Attached Figure Description

[0037] Figure 1 Overall flowchart for data supplementation reporting for the fusion terminal in this application;

[0038] Figure 2 This is a flowchart of the method for supplementing the reporting of integrated terminals in this application. Detailed Implementation

[0039] For different types of electricity meters (485 meters / single-phase meters / three-phase meters), the master station will issue different reporting tasks, including daily freeze reporting tasks and curve data reporting tasks. The fusion terminal needs to report the meter data to the master station after successful data collection.

[0040] The "Object-Oriented Electricity Information Data Exchange Protocol" describes the reporting task in the 601D reporting scheme, which will not be elaborated here. The "Version 22 Acquisition Terminal Protocol Consistency Detection Specification" requires the test device to report several object attributes. If the test device does not respond, the IUT (Integrated Device Unit) will repeatedly report, and the maximum number of reports must be configured. This specification only requires supplementary reporting according to the maximum number of reports in 601D, and the timeout time is the same as the timeout time in 601D. Taking the curve as an example, the timeout time is generally one minute, and the maximum number of reports is three. However, if the master station has problems, it may not be able to reply to the three reporting messages from the fusion terminal within three minutes, or the communication quality may be poor, and the fusion terminal may not receive a reply message from the master station within three minutes, which will still reduce the success rate of reporting meter collection data.

[0041] Based on the above background and problems, the present invention provides a method, system and medium for supplementing missing data reporting in fusion terminals. This enables fusion terminals to supplement unreported daily frozen and curve data of all electricity meters (master meter and household meters) during the day's idle time, ensuring the integrity of daily frozen and curve data and improving the success rate of data collection by the fusion terminals in the main station statistics.

[0042] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are merely some embodiments of the present application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0043] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0044] Example 1

[0045] This application provides a method for supplementing missing data reports in fusion terminal data reporting. Please refer to... Figure 1 , Figure 1 A flowchart of a method for supplementing missing data reporting in a fusion terminal, provided in this application embodiment, is included in the following steps:

[0046] Step S1: When the converged terminal is powered on, if a change in the task scheme or a change in the table file is detected, the reporting task is initialized and the reporting data in the database and the failure list is cleared.

[0047] Specifically, it includes the following steps:

[0048] Step S11: The converged terminal is powered on or detects a change in the task scheme or table file, at which point the initialization reporting task is triggered;

[0049] Step S12: Clear the cached data to be reported in the database and the reported data stored in the failure list;

[0050] Step S13: Based on the latest task plan and table file information, reload and rebuild the configuration of the reporting task, and execute the reporting task.

[0051] In this embodiment, step S1 is a process of re-initializing the reporting task under specific circumstances. In order to ensure that the system can adapt to the latest configuration or file information changes, thereby avoiding problems such as data reporting errors, omissions or duplications caused by old data or outdated configuration, this step clears the old data and reconstructs the reporting task based on the latest configuration to ensure the accuracy and timeliness of data reporting.

[0052] Step S2: After initialization, based on the reporting task and plan, iterate through all ordinary data collection plans and select the plan with the highest matching degree to report the collected data. This specifically includes the following steps:

[0053] S21: The fusion terminal determines whether the current time matches the calculated reporting time of the reporting task;

[0054] S22: Traverse the common collection schemes, and obtain the common collection scheme with the highest matching degree as the matching scheme by comparing the object attribute data in the common collection schemes;

[0055] The acquisition of the matching degree in step S22 specifically includes:

[0056] S221: Obtain the data item identifier of the reporting scheme, and compare the data item identifier of the reporting scheme with the data item identifier of the ordinary acquisition scheme one by one. The data items corresponding to the data item identifier include positive active energy, reverse active energy, voltage, etc.

[0057] S222: Select the common data collection scheme with the largest number of data item identifiers that are the same as the reported scheme as the matching scheme.

[0058] S23: When there are multiple ordinary collection schemes with the same matching degree, the ordinary collection scheme with the same call interval is selected as the matching scheme based on whether the call interval of the ordinary collection scheme and the reporting scheme is the same.

[0059] S23: If the recall intervals of the multiple ordinary acquisition schemes are all different, then compare the recall interval with the recall interval of the reporting scheme, and select the ordinary acquisition scheme whose recall interval is a multiple of the reporting scheme as the matching scheme.

[0060] S24: Frame the data collection and report it.

[0061] In this embodiment, the converged terminal iterates through all ordinary data collection schemes based on the reporting tasks and schemes issued by the master station or in a default file. The default file is a pre-configured set of settings that includes at least reporting tasks and schemes. When the converged terminal starts up, detects changes to a task scheme, or detects changes to a table file, if it has not received any reporting tasks and schemes from the master station, it uses the configurations in these default files to iterate through the ordinary data collection schemes. This helps ensure that even if the network connection is unstable or other reasons prevent timely receipt of master station instructions, the converged terminal can still operate in a predetermined manner.

[0062] In this embodiment, step S2, by matching the collection scheme, can ensure that the reported data meets the requirements of the main station, including data type, recall interval, etc., thereby ensuring the consistency and accuracy of the data.

[0063] Step S3: Store the reported data in the database and create a scheduled task to send the reported data. If the scheduled task receives a reply from the master station after sending the data, delete the reported data in the database and delete the scheduled task that sent the data. If no reply is received from the master station, perform a supplementary report for the scheduled task according to the protocol.

[0064] Specifically, step S3 includes:

[0065] S31: Before reporting data, store the reported data into the database in the polling task that collects the reported data, and at the same time create a scheduled task to send the reported data.

[0066] S32: The fusion terminal sends data to the master station through the timed task and waits to receive a reply from the master station;

[0067] S33: If a reply is received from the master station, delete the scheduled task and delete the reported data already sent by the scheduled task from the database; if no reply is received from the master station, schedule the scheduled task to report the data in accordance with the timeout period of 601D.

[0068] Specifically, the scheduling of this timed task according to the timeout period of 601D includes:

[0069] A timed task is created based on the timeout period of 601D, and the timed task reports data periodically according to the timeout period of 601D.

[0070] If the timeout count reaches 601D, the scheduled task will be deleted.

[0071] According to the scheme of the above embodiment, the reported data is guaranteed to meet the requirements of the main station through scheme matching, and when data loss occurs due to network failure or other reasons, the supplementary reporting function of the scheduled task can promptly supplement the missing data, thereby improving the accuracy and completeness of the data.

[0072] This embodiment enables the automatic resubmission of unreported daily freeze and curve data when the converged terminal is in an abnormal situation, such as poor 4G signal, network interruption, converged terminal malfunction, power outage, etc., ensuring the integrity of daily freeze and curve data and improving the success rate of data collection by the main station for the converged terminal.

[0073] Example 2

[0074] This embodiment provides a method for supplementing missing data reports in fusion terminal data reporting. The method is similar to Embodiment 1, but differs in that, in addition to the scheduled reporting according to the protocol, a failure list supplementation method is added to the self-reporting mechanism to supplement unsuccessfully reported data.

[0075] Step S4: If the number of supplementary reports in step S3 exceeds the timeout number of the 601D reporting scheme, delete the timed task and put the supplementary report data into the failure list for supplementary reporting of the failure list.

[0076] like Figure 2 As shown, in this embodiment, the method for supplementing the failure list of the fusion terminal specifically includes:

[0077] S41: The data in the failure list has the same time period as the normally reported data. Wait for the normally reported data to be reported within the time period.

[0078] S42: After the normal data reporting is completed, the data in the failure list is re-reported. Each re-report counts once. Every T1 time, the failure list is checked to see if the data has been re-reported. If it is found that the data has not been re-reported, a forced re-report is performed.

[0079] S43: Check if the number of data re-reports in the failure list exceeds the maximum number of attempts N and check if the re-reporting was successful within time T2. If the number of re-reports exceeds N and the re-reporting fails within time T2, the data in the failure list is considered redundant data, deleted from the failure list, and no longer reported.

[0080] In this embodiment, the preferred parameters are: T1 is 4 hours, N is 6 times, and T2 is 12 hours.

[0081] In this embodiment, the failure list re-reporting is only executed after ensuring that normal data reporting is completed, so as not to affect the normal task. At the same time, there is a checking mechanism. If the failure list re-reporting mechanism is not executed within 4 hours, a re-reporting is forced, which maximizes the integrity of the reported data.

[0082] This embodiment can effectively prevent resource waste caused by infinite retries by setting the maximum number of retries and the time window, and can store unsuccessfully reported data in the database for 12 hours, increasing the possibility of data being successfully reported in the end.

[0083] This embodiment has been verified in the field. With the addition of the failure list supplementary reporting mechanism, the success rate of data collection by the fusion terminal calculated by the main station has been greatly improved, ensuring the integrity of the reported data.

[0084] It should be noted that in this invention, the fusion terminal executes the reporting task according to the State Grid's "Object-Oriented Electricity Consumption Information Data Exchange Protocol," and performs daily and minute-based data freezing according to the reporting time of the issued reporting task. Furthermore, those skilled in the art should understand that the database is stored in FLASH memory to persistently store all collected data for reporting, while the failure list is stored in memory to record reported data. The failure list has a faster read speed and relies on the database to provide reported data.

[0085] Example 3

[0086] Based on the same inventive concept, this invention provides a system for supplementing missing data reports in integrated terminal data reporting, comprising:

[0087] The initialization module is used to initialize the reporting task and clear the reporting data in the database and linked list when the system boots up, detects changes in the task plan, or detects changes in the table file.

[0088] The matching and reporting module is used to iterate through all ordinary data collection schemes based on the reporting task and scheme, and select the scheme with the highest matching degree to report the collected data.

[0089] The self-reporting module is used to store the reported data into the database and create a scheduled task to send the data. If the scheduled task receives a reply from the master station after sending the data, the data in the database is deleted and the scheduled task for sending the data is deleted. If no reply is received from the master station, the scheduled task is re-reported according to the protocol.

[0090] The failure list reporting module is used to delete the timed task and put the reporting data into the failure list when the number of reporting attempts of the timed task in the self-reporting module exceeds the protocol limit, and to perform failure list reporting.

[0091] Furthermore, the matching reporting module includes:

[0092] The first selection unit is used to traverse the common collection schemes and obtain the common collection scheme with the highest matching degree as the matching scheme by comparing the object attribute data in the common collection schemes.

[0093] The second selection unit is used to select the ordinary collection scheme with the same call interval as the reporting task as the matching scheme when there are multiple ordinary collection schemes with the same matching degree.

[0094] The third selection unit is used to select the ordinary acquisition scheme whose recall interval is a multiple of the reporting task recall interval as the matching scheme when the recall intervals of the multiple ordinary acquisition schemes are all different.

[0095] The failure list replenishment module is used to delete the scheduled task and put the replenishment data into the failure list to perform failure list replenishment.

[0096] Those skilled in the art will clearly understand that, for convenience and brevity, the specific working process of the above-described device can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0097] Furthermore, the method for supplementing missing data reporting in converged terminal data 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, causes the processor to perform the method for supplementing missing data reporting in converged terminal data as described above.

[0098] 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.

[0099] 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.

[0100] The foregoing has provided a detailed description of the method, system, and medium for supplementing missing data reporting in a converged terminal, as provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and its core ideas. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A method for supplementing missing data reporting in integrated terminal data reporting, characterized in that, For use in converged terminals, the following steps are included: Step S1: When the system is powered on, a change in the task plan is detected, or a change in the table file is detected, the initialization of the reporting task is performed, and the reporting data in the database and linked list is cleared. Step S2: Based on the reporting task and plan, traverse all ordinary data collection plans, select the matching plan, and report the collected data. Step S3: Store the reported data in the database and create a scheduled task to send the data. If the scheduled task receives a reply from the master station after sending the data, delete the data in the database and delete the scheduled task to send the data. If no reply is received from the master station, perform a supplementary report for the scheduled task according to the protocol. Step S4: If the number of times the scheduled task is re-reported in step S3 exceeds the timeout number of the 601D reporting scheme, delete the scheduled task and put the re-reported data into the failure list, and perform failure list re-reporting. The failure list replenishment process in step S4 specifically includes the following steps: S41: The data in the failure list follows the time period of the normal data report and waits for the normal data report to be completed within the time period; S42: After the normal data reporting is completed, the data in the failure list is reported. Every T1 time, the data in the failure list is checked to see if it has been re-reported. If it has not been re-reported, it is forced to be re-reported once. S43: Check if the number of times the data in the failure list has been reported exceeds N and whether the report was successfully reported within time T2. If it is unsuccessful, the data in the failure list is considered redundant and deleted from the failure list.

2. The method for supplementing missing data reporting in a fusion terminal according to claim 1, characterized in that, Step S2 includes: S21: Determine if the current time matches the reporting time of the reporting task; S22: Traverse the common collection schemes, and obtain the common collection scheme with the highest matching degree as the matching scheme by comparing the object attribute data in the common collection schemes.

3. The method for supplementing missing data reporting in a fusion terminal according to claim 2, characterized in that, Step S2 further includes: S23: When there are multiple ordinary collection schemes with the same matching degree, the ordinary collection scheme with the same call interval as the reporting task shall be selected as the matching scheme. S24: If the recall intervals of the multiple common acquisition schemes are all different, then the common acquisition scheme whose recall interval is a multiple of the reporting task recall interval is selected as the matching scheme.

4. The method for supplementing missing data reporting in a fusion terminal according to claim 1, characterized in that, If no response is received from the main station in step S3, a timed task report is performed according to 601D. The interval of the timed task is the timeout period specified by 601D, and the number of reports is the number of reports required by 601D.

5. A method for supplementing missing data reporting in a fusion terminal according to claim 2 or 3, characterized in that, The acquisition of the matching scheme in step S22 specifically includes: S221: Obtain the data item identifier of the reporting scheme and compare the data item identifier of the reporting scheme with the data item identifier of the ordinary collection scheme one by one; S222: Select the common data collection scheme with the largest number of data item identifiers that are the same as the reported scheme as the matching scheme.

6. A system for supplementing missing data reporting from integrated terminals, characterized in that, include: The initialization module is used to initialize the reporting task and clear the reporting data in the database and linked list when the system boots up, detects changes in the task plan, or detects changes in the table file. The matching and reporting module is used to iterate through all ordinary data collection schemes based on the reporting task and scheme, and select the matching scheme to report the collected data. The self-reporting module is used to store the reported data into the database and create a scheduled task to send the data. If the scheduled task receives a reply from the main station after sending the data, the data in the database is deleted and the scheduled task for sending the data is also deleted. If no reply is received from the main site, the scheduled task will be submitted in accordance with the agreement. The failure list reporting module is used to delete the timed task and put the reporting data into the failure list when the number of reporting attempts of the timed task in the self-reporting module exceeds the protocol limit, and to perform failure list reporting. The failure list reporting module includes: The waiting unit is used to make the data in the failure list follow the time period of the normally reported data, and wait for the normally reported data to be reported within the time period. The supplementary reporting unit is used to report the data in the failure list after the normal data reporting is completed. It checks whether the data in the failure list has been supplemented every T1 time. If it has not been supplemented, it forces a supplementary report. The checking unit is used to check whether the number of times the data in the failure list has been reported exceeds N and whether the report was successfully reported within time T2. If it is unsuccessful, the data in the failure list is regarded as redundant data and deleted from the failure list.

7. The system for supplementing missing data reporting in fusion terminal data reporting according to claim 6, characterized in that, The matching and reporting module includes: The first selection unit is used to traverse the common collection schemes and obtain the common collection scheme with the highest matching degree as the matching scheme by comparing the object attribute data in the common collection schemes. The second selection unit is used to select the ordinary collection scheme with the same call interval as the reporting task as the matching scheme when there are multiple ordinary collection schemes with the same matching degree. The third selection unit is used to select the ordinary acquisition scheme whose recall interval is a multiple of the reporting task recall interval as the matching scheme when the recall intervals of the multiple ordinary acquisition schemes are all different.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium has a computer program that, when executed by a processor, implements a method for supplementing missing data reporting in a converged terminal as described in any one of claims 1-4.

Images