Method and system for supplementing missing report of data report of fusion terminal, and medium

Abstract

The invention relates to the technical field of fusion terminals, and particularly provides a fusion terminal data reporting missing rereporting method and system and a medium, and the method comprises the steps: through a reporting task initialization mechanism, when a fusion terminal is started or a task scheme and a table file change, emptying historical data and carrying out initialization again; adopting an acquisition scheme matching strategy based on the matching degree and the interrogation interval to accurately select a target acquisition scheme; in combination with a two-stage compensation mechanism of self-compensation and failure linked list compensation, compensation is scheduled according to protocol timeout in the self-compensation stage, and periodic compensation, forced compensation and redundant data cleaning are executed in the failure linked list stage. Through the above steps, the integrity and reliability of data reporting of the fusion terminal are effectively improved, and the accuracy of collection success rate statistics of the master station is guaranteed.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of fusion terminals, and particularly relates to a method and system for reporting missing data of a fusion terminal and a medium. BACKGROUND

[0002] As a core function of the fusion terminal, the stable operation of data reporting is directly related to the completeness and accuracy of power consumption data collection. In the normal workflow, the fusion terminal needs to match the execution rules from the set meter reading scheme of the master station according to the pre-configured reporting task and the corresponding reporting scheme of the master station. When the reporting task trigger time arrives, the fusion terminal will extract the collected meter data and perform data upload operation according to the reporting scheme bound to the task.

[0003] However, the complexity of the field operation environment often leads to abnormal data reporting. In the meter reading and reporting process, 4G signal is weak, network burst interruption, fusion terminal itself failure or power supply interruption and other situations occur frequently, which will directly cause data reporting missing and further affect the statistical accuracy of the master station on the collection success rate of the fusion terminal.

[0004] In order to protect the reliability of data reporting, the "22 version collection terminal protocol consistency detection specification" clearly stipulates that the reporting process needs to perform the reporting mechanism according to the maximum number set in the protocol field 601D, and the timeout time also follows the configuration of the field. Taking the curve data reporting as an example, the conventional configuration is 1 minute for the timeout time and 3 times for the maximum number of reporting. However, there are uncontrollable factors in actual application: if the master station has processing delay or failure, it may cause the master station to fail to respond to the 3 reporting messages of the fusion terminal within 3 minutes; or due to poor communication link quality, the fusion terminal cannot receive the reply of the master station within the 3-minute reporting window. The above situations will cause the failure of meter data reporting, and finally reduce the collection success rate of the fusion terminal. SUMMARY

[0005] In order to solve the problems existing in the prior art, the application provides a method for reporting missing data of a fusion terminal, which is used for the fusion terminal and includes the following steps: Step S1, when booting, detecting task scheme change or detecting meter file change, initializing the reporting task, and emptying the reporting data in the database and the linked list; Step S2, according to the reporting task and the scheme, traversing all normal collection schemes, selecting the matching scheme to report the collected data; Step S3, storing the reporting data into the database, and creating a timing task for sending data, if the master station replies after the timing task sends data, deleting the data in the database and deleting the timing task for sending data; if no reply of the master station is received, performing the reporting of the timing task according to the protocol; Step S4, if the number of times of the timing task in step S3 exceeds the timeout number of the 601D reporting scheme, deleting the timing task and putting the reporting data into a failure chain table for failure chain table reporting.

[0006] On the basis of the above scheme, the failure chain table reporting in step S4 specifically includes the following steps: S41: the data in the failure chain table follows the time period of normal reporting data, and the normal reporting data is waited to be reported in the time period; S42: after the normal reporting data is reported, the data in the failure chain table is reported, and the data in the failure chain table is checked every T1 time to see if it is reported, and if not, it is forced to report once; S43: check if the number of times of the data in the failure chain table exceeds N and if it is successfully reported within T2 time, if not, the data in the failure chain table is regarded as redundant data and is deleted from the failure chain table.

[0007] Further, the step S2 includes: S21: judging whether the current time meets the reporting time of the reporting task; S22: traversing the normal collection scheme, and obtaining the normal collection scheme with the highest matching degree as the matching scheme by comparing the object attribute data in the normal collection scheme.

[0008] Preferably, the step S2 further includes: S23: when there are multiple normal collection schemes with the same matching degree, the normal collection scheme is selected as the matching scheme according to whether the polling interval is the same as the reporting task; S24: if the polling intervals of the multiple normal collection schemes are all different, the normal collection scheme with the polling interval in multiple relationship with the reporting task polling interval is the matching scheme.

[0009] On the basis of the above scheme, if no reply is received from the host station, the timing task is reported according to 601D, the interval time of the timing task is the timeout time specified by 601D, and the number of times of reporting is the number of times of reporting of 601D.

[0010] Preferably, the obtaining of the matching scheme in step S22 specifically includes: S221: obtaining the data item identifier of the reporting scheme, and comparing the data item identifier of the reporting scheme with the data item identifier of the normal collection scheme one by one; S222: selecting the normal collection scheme with the largest number of the same data item identifier as the matching scheme.

[0011] Based on the same inventive concept, the present application provides a system for reporting missing terminal data, comprising: The initialization module is configured to initialize the reporting task, clear the reporting data in the database and the linked list when booting, detecting a change in the task scheme or detecting a change in the table file; The matching reporting module is configured to traverse all the normal collection schemes according to the reporting task and the scheme, and select a matching scheme to report the collected data; The self-reporting module is configured to store the reporting data in the database, and create a timing task for sending data, if the timing task sends data and receives a reply from the master station, delete the data in the database and the timing task for sending data, if no reply from the master station is received, perform the self-reporting of the timing task according to the protocol; The failure linked list reporting module is configured to delete the timing task and put the reporting data in the failure linked list when the number of self-reporting of the timing task in the self-reporting module exceeds the number specified in the protocol, and perform the failure linked list reporting.

[0012] Further, the matching reporting module comprises: The first selection unit is configured to traverse the normal collection schemes, and obtain the normal collection scheme with the highest matching degree as the matching scheme by comparing the object attribute data in the normal collection schemes; The second selection unit is configured to select the normal collection scheme with the same measurement interval as the reporting task as the matching scheme when there are multiple normal collection schemes with the same matching degree; The third selection unit is configured to select the normal collection scheme with the measurement interval in a multiple relationship with the measurement interval of the reporting task as the matching scheme when the measurement intervals of the multiple normal collection schemes are all different.

[0013] The application further provides a computer readable storage medium, which has a computer program, and the computer program is executed by a processor to realize the steps of the method for reporting missing data of a fusion terminal.

[0014] Compared with the prior art, the application has the following beneficial effects: 1. In the abnormal case of the fusion terminal, the automatic reporting of the unreported daily freeze and curve data is realized, the integrity of the daily freeze and curve data is ensured, and the success rate of collecting the fusion terminal by the master station is improved; 2. The failure linked list reporting mechanism is proposed on the basis of the self-reporting, the unreported data can be stored in the database for 12 hours without affecting the normal reporting task, and the integrity of the reporting data is maximally ensured. BRIEF DESCRIPTION OF DRAWINGS

[0015] Figure 1 The whole flowchart of the data reporting of the fusion terminal is shown in the application; Figure 2 The flowchart of the fusion terminal supplementary reporting method is shown in the present application. DETAILED DESCRIPTION

[0016] For different electric meters (485 meters / single-phase meters / three-phase meters), the main station will issue different reporting tasks, including daily frozen reporting tasks and curve data reporting tasks, etc. The fusion terminal needs to report the electric meter data to the main station after successful collection.

[0017] The reporting task is described in the 601D reporting scheme in the Object-Oriented Electricity Information Data Exchange Protocol, which is not specifically described here. The 22nd Edition of the Collection Terminal Protocol Consistency Detection Specification requires the test equipment to report a number of object attributes, the test equipment does not respond, the IUT repeatedly reports, and reports according to the configured maximum number of reporting times. The technical specification only requires reporting according to the maximum number of 601D to make up for the report, and the timeout time is the timeout time in 601D. Taking the curve as an example, the timeout time is generally one minute, and the maximum reporting times is three times. However, if the main station has a problem, it may not be able to reply to the 3 times of reporting messages of the fusion terminal within 3 minutes, or the communication quality is poor, and the fusion terminal cannot receive the reply message of the main station within 3 minutes, which will still reduce the success rate of reporting the electric meter collection data.

[0018] Based on the above background and problems, the present application provides a fusion terminal data reporting missing supplementary reporting method, system and medium, which realizes the fusion terminal to report the daily frozen and curve data of all electric meters (total meter and household meter) that have not been successfully reported in the idle time of the day, guarantees the integrity of the daily frozen and curve data, and improves the success rate of the main station to collect the fusion terminal.

[0019] In order to make the personnel in the technical field better understand the present application, the present application will be further described in detail below in combination with the drawings and specific embodiments. Obviously, the described embodiments are only part of the embodiments of the present application, not all. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0020] In the following description, many specific details are set forth in order to provide a thorough understanding of the present application, but the present application can also be implemented in other ways different from those described herein, and those skilled in the art can make similar generalizations without departing from the concept of the present application, therefore the present application is not limited to the specific embodiments disclosed below.

[0021] Embodiment 1 The present application provides a fusion terminal data reporting missing supplementary reporting method, please refer to Figure 1 , Figure 1A method flowchart for reporting missing data of a fusion terminal is provided in the embodiments of the present application, and the method comprises the following steps: In step S1, when the fusion terminal is powered on, the initialization of the reporting task is performed and the reporting data in the database and the failure linked list is emptied when the task scheme is detected to be changed or the table file is detected to be changed.

[0022] Specifically, the following steps are included: In step S11, the initialization of the reporting task is triggered when the fusion terminal is powered on or the task scheme or the table file is detected to be changed. In step S12, the cached reporting data in the database and the reporting data stored in the failure linked list are emptied. In step S13, the configuration of the reporting task is reloaded and constructed according to the latest task scheme and table file information, and the reporting task is executed.

[0023] In the embodiments, step S1 is a process of reinitializing the reporting task in a specific case. In order to ensure that the system can adapt to the latest configuration or file information, the data reporting errors, omissions or repetitions caused by old data or outdated configurations are avoided, and the accuracy and timeliness of data reporting are ensured by emptying the old data and reconstructing the reporting task based on the latest configuration.

[0024] In step S2, after the initialization is completed, all normal collection schemes are traversed according to the reporting task and scheme, and the scheme with the highest matching degree is selected for collecting and reporting data, which specifically comprises the following steps: In S21, the fusion terminal judges whether the current time conforms to the reporting time of the calculated reporting task. In S22, the normal collection schemes are traversed, and the normal collection scheme with the highest matching degree is obtained as the matching scheme by comparing the object attribute data in the normal collection schemes. The acquisition of the matching degree in step S22 specifically comprises: In S221, the data item identifier of the reporting scheme is obtained, and the data item identifier of the reporting scheme is compared with the data item identifier of the normal collection scheme one by one. The data item corresponding to the data item identifier includes positive active electric energy, negative active electric energy, voltage, etc. In S222, the normal collection scheme with the largest number of the same data item identifiers as the reporting scheme is selected as the matching scheme.

[0025] In S23, when there are multiple normal collection schemes with the same matching degree, the normal collection scheme with the same measurement interval as the reporting scheme is selected as the matching scheme according to whether the measurement intervals of the normal collection scheme and the reporting scheme are the same. S23: If the call-measuring intervals of the plurality of normal collection schemes are all different, compare the call-measuring intervals with the call-measuring interval of the reporting scheme, and select the normal collection scheme having a call-measuring interval that is a multiple of the call-measuring interval of the reporting scheme as the matching scheme; S24: Frame the collected data for reporting.

[0026] In this embodiment, the fusion terminal traverses all normal collection schemes according to the reporting tasks and schemes in the default file or the reporting tasks and schemes issued by the main station. The default file is a set of pre-configured configurations, and at least contains reporting tasks and schemes. When the fusion terminal starts, detects a change in the task scheme, or detects a change in the table file, if no reporting tasks and schemes are received from the main station, the configurations in the default file are used to traverse the normal collection schemes. This helps to ensure that even if the network connection is unstable or other reasons cause the main station instructions to be unable to be received in time, the fusion terminal can still operate in a predetermined manner.

[0027] In this embodiment, step S2 traverses the collection schemes by matching, which can ensure that the reported data meets the requirements of the main station, including data types, call-measuring intervals, etc., thereby ensuring the consistency and accuracy of the data.

[0028] Step S3 stores the reported data in the database, and creates a timing task for sending the reported data: if a reply from the main station is received after the timing task sends the data, the reported data in the database is deleted and the timing task for sending the data is deleted; if no reply from the main station is received, the reported data is reported according to the protocol.

[0029] Specifically, step S3 includes: S31: Before reporting the data, store the reported data in the database in the polling task for collecting the reported data, and create a timing task for sending the reported data; S32: The fusion terminal sends the data to the main station through the timing task, and waits to receive a reply from the main station; S33: If a reply from the main station is received, the timing task is deleted, and the reported data sent by the timing task in the database is deleted; if no reply from the main station is received, the reported data is reported according to the timeout time of 601D.

[0030] Specifically, the scheduling of the timing task according to the timeout time of 601D includes: Create a timing task according to the timeout time of 601D, and the timing task reports the data according to the timeout time of 601D; If the timeout time of 601D is reached, the timing task is deleted.

[0031] 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 reporting function of the timing task can timely supplement the missing data, thereby improving the accuracy and integrity of the data.

[0032] The embodiment realizes automatic reporting of the unreported daily freeze and curve data in abnormal conditions such as poor 4G signal, network interruption, abnormal fusion terminal, power failure and the like, guarantees the integrity of the daily freeze and curve data, and improves the success rate of the main station in collecting the fusion terminal.

[0033] Embodiment 2 The embodiment provides a method for reporting missing data of a fusion terminal, which refers to embodiment 1, and differs from embodiment 1 in that, on the basis of reporting the timing task according to the protocol, in order to realize reporting of the unreported data, a failure chain table reporting method is added on the basis of self-reporting: In step S4, if the number of times of reporting exceeds the timeout number of the reporting scheme, the timing task is deleted and the reported data is put into the failure chain table for failure chain table reporting.

[0034] As shown in Figure 2 In the embodiment, the method for reporting missing data of the fusion terminal specifically includes: S41: The data in the failure chain table has the same time period as the normal reported data, and the normal reported data is waited to be reported in the time period; S42: After the normal reported data is reported, the data in the failure chain table is reported, and the number of times of reporting is counted once for each time of reporting; the data in the failure chain table is checked every T1 time to see whether the data is reported or not, and if the data is not reported, the data is forcibly reported once; S43: Whether the number of times of reporting the data in the failure chain table exceeds the maximum number of attempts N and whether the data is successfully reported within T2 time are checked, if the number of times of reporting exceeds N times and the data is not successfully reported within T2 time, the data in the failure chain table is regarded as redundant data, and the data is deleted from the failure chain table, and the data in the failure chain table is not reported.

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

[0036] The failure chain table reporting in the embodiment needs to be executed under the condition that the normal data reporting is completed, and does not affect the normal task, and at the same time, there is a checking mechanism, and if the failure chain table reporting mechanism is not executed within 4 hours, the reporting is forcibly executed once, thereby maximizing the integrity of the reported data.

[0037] The embodiment can effectively prevent resource waste caused by infinite retries by setting the maximum number of retries and the time window, and can store the data that is not successfully reported in the database for 12 hours, thereby increasing the possibility of final successful reporting of data.

[0038] The embodiment is verified in the field, and after the failure chain table supplement reporting mechanism is added, the success rate of the fusion terminal collected by the master station is greatly improved, thereby ensuring the integrity of the reported data.

[0039] It should be noted that the fusion terminal in the application executes the reporting task according to the State Grid's Object-oriented Electricity Information Data Exchange Protocol, and performs daily freezing and minute freezing data reporting according to the reporting time of the issued reporting task. In addition, those skilled in the art should be aware that the database is stored in FLASH and is used to persistently save all collected data for reporting, and the failure chain table is stored in the memory and records the reporting data. The failure chain table has a faster reading speed, and the failure chain table depends on the database to provide reporting data.

[0040] Embodiment 3 Based on the same inventive concept, the application provides a system for supplement reporting of missing fusion terminal data, comprising: An initialization module, configured to initialize the reporting task when starting, detecting a change in a task scheme or detecting a change in a table file, and clear the reporting data in the database and the chain table; A matching reporting module, configured to traverse all normal collection schemes according to the reporting task and the scheme, and select the scheme with the highest matching degree to report the collected data; A self-supplement reporting module, configured to store the reporting data into the database, and create a timing task for sending data. If a reply from the master station is received after the timing task sends the data, the data in the database is deleted and the timing task for sending data is deleted. If no reply from the master station is received, the timing task is supplemented according to the protocol; A failure chain table supplement reporting module, configured to delete the timing task and put the supplement reporting data into the failure chain table for failure chain table supplement reporting when the number of supplement reporting of the timing task in the self-supplement reporting module exceeds the number specified in the protocol.

[0041] Further, the matching reporting module comprises: A first selection unit, configured to traverse the normal collection schemes, and obtain the normal collection scheme with the highest matching degree as the matching scheme by comparing the object attribute data in the normal collection schemes; A second selection unit, configured to select the normal collection scheme with the same measurement interval as the reporting task as the matching scheme when there are multiple normal collection schemes with the same matching degree. The third selection unit is configured to select, when the measurement intervals of the plurality of normal collection schemes are all different, a normal collection scheme with a measurement interval that is a multiple of the reporting task measurement interval as the matching scheme.

[0042] The failure list supplement reporting module is configured to delete the timing task and put the supplement data into the failure list for failure list supplement reporting.

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

[0044] In addition, the fusion terminal data reporting loss supplement method according to the present application can be recorded in a computer readable recording medium. Specifically, according to the present application, a computer readable recording medium storing computer executable instructions can be provided, which can cause a processor to execute the fusion terminal data reporting loss supplement method as described above when the computer executable instructions are executed by the processor.

[0045] It should be noted that the flowcharts and block diagrams in the drawings illustrate the possible architectural, functional, and operational scenarios of systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flowcharts or block diagrams can represent a module, a program segment, or a portion of code that includes at least one executable instruction for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in different orders than those noted in the drawings. For example, two blocks that are shown in succession can actually be executed substantially in parallel, and sometimes in reverse order, depending on the involved functions. 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 by a dedicated hardware-based system that performs the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0046] Generally, the various example embodiments of the present application can be implemented in hardware or special-purpose circuits, software, firmware, logic, or any combination thereof. Some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software which can be executed by a controller, microprocessor or other computing device. Where the embodiments of the present application are illustrated in the form of a block diagram, a flowchart, or using some other pictorial representation, it will be understood that the blocks, apparatus, systems, techniques or methods described herein can be implemented in hardware, software, firmware, special-purpose circuits, or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0047] The above describes in detail a method, system and medium for reporting missing data reporting of a fusion terminal provided by the present application. The principles and implementation modes of the present application are described by applying specific examples. The above description of the embodiments is only used to help understand the method of the present application and its core idea. It should be pointed out that, for those skilled in the art, without departing from the principles of the present application, some improvements and modifications can be made to the present application, and these improvements and modifications also fall within the protection scope of the claims of the present application.

Claims

1. A method for reporting missing data reporting of a fusion terminal, characterized in that, A method for a fusion terminal, comprising the following steps: Step S1, when booting, detecting a task scheme change or detecting a table file change, performing initialization of a reporting task, and emptying reporting data in a database and a linked list; Step S2, according to the reporting task and a scheme, traversing all normal collection schemes, and selecting a matching scheme to report collected data; Step S3, storing the reporting data into the database, and creating a timing task for sending data, if a reply from a master station is received after the timing task sends data, deleting the data in the database and the timing task for sending data, and if no reply from the master station is received, performing a reporting task according to a protocol; Step S4, if a number of times of the reporting task exceeds a timeout number of the reporting scheme, deleting the reporting task and putting the reporting data into a failure linked list, and performing a failure linked list reporting task.

2. The method for reporting missing data of a fusion terminal according to claim 1, wherein, The failure linked list reporting task in step S4 specifically comprises the following steps: S41, the data in the failure linked list follows a time period of normal reporting data, and the data in the failure linked list is waited for reporting completion within the time period; S42, after the normal reporting data is reported, the data in the failure linked list is reported, and the data in the failure linked list is checked every T1 time to see if the data is reported, and if not, the data is forced to be reported once; S43, if a number of times of reporting the data in the failure linked list exceeds N and if the data is successfully reported within T2 time, the data in the failure linked list is considered as redundant data and is deleted from the failure linked list.

3. The method for reporting missing data of a fusion terminal according to claim 1, wherein, The step S2 comprises: S21, judging whether a current time meets a reporting time of the reporting task; S22, traversing the normal collection schemes, and obtaining a normal collection scheme with a highest matching degree as a matching scheme by comparing object attribute data in the normal collection schemes.

4. The method for reporting missing data of a fusion terminal according to claim 3, wherein, The step S2 further comprises: S23, when there are multiple normal collection schemes with the same matching degree, selecting a normal collection scheme with a same measurement interval as a measurement interval of the reporting task as the matching scheme; S24, if the multiple normal collection schemes all have different measurement intervals, selecting a normal collection scheme with a measurement interval in a multiple relationship with the measurement interval of the reporting task as the matching scheme.

5. The method for reporting missing data of a fusion terminal according to claim 1, wherein, If no reply from the master station is received, the step S3 performs a reporting task according to 601D, an interval time of the reporting task is a timeout time specified by 601D, and a number of times of reporting is a number of times of reporting specified by 601D.

6. The method for reporting missing data of a fusion terminal according to claim 3 or 4, characterized in that, The step S22 specifically comprises: S221, obtaining data item identifiers of the reporting scheme, and comparing the data item identifiers of the reporting scheme with data item identifiers of the normal collection schemes one by one; S222, selecting a normal collection scheme with a same number of data item identifiers as the reporting scheme as the matching scheme.

7. A system for reporting missing data reporting of a fusion terminal, characterized in that, The method comprises: an initialization module, configured to perform initialization of a reporting task, and emptying reporting data in a database and a linked list when booting, detecting a task scheme change or detecting a table file change; a matching reporting module, configured to traverse all normal collection schemes according to a reporting task and a scheme, and select a matching scheme to report collected data; and The self-supplement reporting module is configured to store the reported data into a database and create a timing task for sending data, and if the timing task receives a reply from the master station after sending the data, the data in the database is deleted and the timing task for sending data is deleted. If no reply is received from the master station, the timing task is supplemented according to the protocol. The failure list supplement reporting module is configured to delete the timing task and put the supplement data into a failure list for failure list supplement reporting when the number of supplement times of the timing task in the self-supplement reporting module exceeds the number of supplement times specified in the protocol.

8. The system for reporting missing data reporting of the fusion terminal according to claim 7, wherein, The matching reporting module comprises: The first selection unit is configured to traverse the normal collection schemes, compare the object attribute data in the normal collection schemes, and obtain a normal collection scheme with the highest matching degree as a matching scheme. The second selection unit is configured to select a normal collection scheme with the same measurement interval as the reporting task as the matching scheme when there are multiple normal collection schemes with the same matching degree. The third selection unit is configured to select a normal collection scheme with a measurement interval that is a multiple of the measurement interval of the reporting task as the matching scheme when the measurement intervals of the multiple normal collection schemes are all different.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium has a computer program, and the computer program is executed by the processor to realize the method for supplementing missing data reporting of a fusion terminal according to any one of claims 1-6.

Images