Meter task configuration method and system

Abstract

The embodiment of the invention discloses a meter task configuration method and system. The method comprises the steps that a meter list sent by an electricity meter master station is received, the meter list comprises electricity meter information and meter tasks corresponding to the electricity meter information, the meter tasks comprise task numbers and collection tasks corresponding to the task numbers, and the collection tasks comprise at least one OBIS curve arranged in sequence; the method further includes sending a meter task to a corresponding ammeter based on the ammeter information. In addition, the method further comprises the step of retransmitting the related meter task to the corresponding electricity meter based on the electricity meter information of the electricity meter with the failed feedback result in response to the fact that the feedback result returned by the electricity meter is failure. Through the mode, the ammeter master station issues the meter list to the ammeter through the concentrator, and a response failure result can be retransmitted and issued by the concentrator, so that the sending and receiving feedback path is shortened, the meter task issuing efficiency is improved, the resource occupation of the ammeter master station is reduced, and the operation of other functions of the master station is not influenced.

Description

Technical Field

[0001] The present disclosure relates to the field of remote communication control of electric meters, and more particularly, to a method and system for configuring meter tasks. Background Art

[0002] Generally, the master station of the electric meter issues meter tasks to the terminal electric meters through the concentrator. The terminal electric meters execute relevant collection tasks according to the meter tasks. In the scenario where the downlink communication between the concentrator and the electric meter is very poor and the meter tasks cannot be successfully issued, the master station of the electric meter needs to resend multiple times until all meter tasks are successfully issued. In this way, a large amount of resources of the master station will be occupied, and even the execution of other tasks of the master station will be affected. Moreover, the long resending communication path and feedback path lengthen the issuing and feedback time, and there are also many communication instability factors, resulting in a reduction in the issuing efficiency of meter tasks. Summary of the Invention

[0003] One or more embodiments of the present disclosure describe a method and system for configuring meter tasks, aiming to solve one or more of the above problems and other potential problems.

[0004] In the first aspect of the present disclosure, a method for configuring meter tasks is provided. The method includes receiving a meter list sent by the master station of the electric meter, where the meter list includes meter information and meter tasks corresponding to the meter information. The meter tasks include a task number and a collection task corresponding to the task number, and the collection task includes at least one OBIS curve arranged in sequence. The method further includes sending the meter tasks to the corresponding electric meters based on the meter information. In addition, the method further includes, in response to the feedback result returned by the electric meter being a failure, retransmitting the relevant meter tasks to the corresponding electric meters based on the meter information of the electric meters with the feedback result being a failure.

[0005] In the second aspect of the present disclosure, a system for configuring meter tasks is provided. The system includes a master station of the electric meter, a concentrator, and a plurality of electric meters. The master station of the electric meter is used to form a meter list based on the updated information of the meter tasks, and the master station of the electric meter is further used to send the meter list to the concentrator, and the concentrator configures the meter tasks for the electric meters based on the method described in the first aspect.

[0006] In the third aspect of the present disclosure, a computer program product is provided, including a computer program, and the computer program is executed by a processor to implement the method according to the first aspect.

[0007] In the fourth aspect of the present disclosure, a machine-readable storage medium is provided. Machine-executable instructions are stored on the machine-readable storage medium, and the machine-executable instructions are executed by a processor to implement the method provided in the first aspect of the present disclosure.

[0008] It should be understood that the content described in the Summary of the Invention section is not intended to limit the key or important features of the embodiments of the present disclosure, nor to limit the scope of the present disclosure. Other features of the present disclosure will become readily apparent from the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] To more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following briefly introduces the drawings required for the embodiments. Obviously, the drawings in the following description are only some embodiments of the present disclosure. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0010] Figure 1 A schematic diagram showing an exemplary environment in which some embodiments of the present disclosure can be implemented; Figure 2 A flowchart showing a method for configuring a meter task according to some embodiments of the present disclosure; Figure 3 A schematic diagram showing the multi-terminal interaction process of a meter master station, a concentrator, and meters according to some embodiments of the present disclosure; Figure 4 A schematic diagram showing the overall logical judgment of a retransmission process according to some embodiments of the present disclosure; Figure 5 An exemplary schematic diagram showing a retransmission process according to some embodiments of the present disclosure; Figure 6 An exemplary schematic diagram showing the formation process of a new meter list according to some embodiments of the present disclosure; Figure 7 An exemplary schematic diagram showing the formation process of a supplementary transmission task according to some embodiments of the present disclosure; Figure 8 A block diagram showing the structure of a meter task configuration system according to some embodiments of the present disclosure; Figure 9 A schematic diagram showing the task template configuration interface of a meter master station according to some embodiments of the present disclosure; Figure 10 A schematic diagram showing the configuration process of a meter list according to some embodiments of the present disclosure; and Figure 11 A block diagram showing an electronic device that can implement multiple embodiments of the present disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0011] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not used to limit the protection scope of the present disclosure.

[0012] In the description of the embodiments of the present disclosure, the term "including" and its similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc. may refer to different or the same objects. There may also be other explicit and implicit definitions below.

[0013] Generally, the electricity meter has been configured with relevant meter tasks based on the factory task template before leaving the factory. The meter tasks include power metering (including active power metering, reactive power metering, time-of-use metering, ladder price metering, etc.), parameter configuration (including operating parameters of the electricity meter, etc.), data collection and storage (including real-time data collection, historical data storage, frozen data, etc.), status monitoring and fault diagnosis (including electricity meter operating status monitoring, fault detection, abnormal alarm, etc.). When put into use after leaving the factory, due to different requirements of end users, it is often necessary to configure the end electricity meter as needed.

[0014] When the master meter station issues a meter task to the terminal meter, it usually transmits the task to the terminal meter through the concentrator in a transparent transmission mode. In the transparent transmission mode, the concentrator only serves as a data relay station and forwards the received data to the terminal meter without any changes. The master meter station communicates with the concentrator in the upstream direction, and the upstream communication is generally achieved by using GPRS or Ethernet, and the communication situation is generally good. The concentrator communicates with the meter in the downstream direction, and the downstream communication is generally achieved by using G3-PLC (the third-generation power line communication technology) or BPLC (Broadband Power Line Communication technology). Due to the complex on-site environment, various factors such as impedance, attenuation, and noise may cause poor communication at certain times. For example, the turning on of LED street lights will introduce very serious noise, resulting in the inability of PLC to communicate during the period when the street lights are turned on. The success rate of the task during this period is almost 0, and operations can only be carried out during other periods. For a delivery site with tens of thousands of meters, it is time-consuming and laborious and ineffective to rely on manual selection of periods for re-operation. During this process, the issuing path and the feedback path are relatively long, and combined with the unstable factors of the downstream communication, it causes a relatively long issuing time for the meter task, low issuing efficiency, and a relatively high issuing failure rate. Although relying on other periods to re-issue the meter task can avoid communication failures to a certain extent, each re-issuing depends on the master meter station. For tens of thousands of issuing objects and issuing information, the master station needs to have a relatively high operating capacity, otherwise it will greatly affect the normal operation of other functions of the master meter station. In addition, during the issuing process of the meter task, there may also be a situation where the downstream communication is good, but the terminal meter fails to configure the meter task. Based on this feedback situation, the master meter station needs to re-issue the meter task for configuration. Due to the occasional poor communication and various random configuration failures during the issuing process of the meter task, the existing issuing communication mode results in low efficiency of issuing and re-issuing the meter task, and a relatively low success rate.

[0015] Therefore, an embodiment of the present disclosure proposes a method for configuring a meter task. This method can configure the meter task issued by the master meter station in the concentrator, and mainly relies on the concentrator to issue the meter task to the corresponding terminal meter. Even in the case of feedback results failure such as poor communication or configuration failure, the concentrator can automatically respond and re-issue the failed meter task to the corresponding terminal meter.

[0016] In this way, the concentrator receives the meter task configured by the master meter station and, as the sender and re-transmitter, sends the meter task to tens of thousands of terminal meters. This not only reduces the resource occupancy of the master meter station, ensuring that the master meter station can take into account the operation of other functions, such as meter task configuration, meter operation status monitoring, etc., but also can shorten the issuing and feedback paths, improve the issuing and re-issuing efficiency, and be able to issue the meter task relatively many times within a certain period, improving the issuing success rate.

[0017] Figure 1 FIG. is a schematic diagram of an exemplary environment 100 in which some embodiments of the present disclosure may be implemented. As Figure 1 shown, the environment 100 includes a master meter station 102, which is typically the core system re-used by the power system for centralized management and control of meter data, and generally runs on a server or a computer cluster. The server or computer cluster needs to have powerful computing capabilities and storage capabilities to handle a large amount of data and concurrent tasks. The environment 100 also includes a concentrator 104 that communicates upstream 108 with the master meter station 102, typically via 2G / 3G / 4G / 5G. The environment 100 also includes a plurality of meters 106-1, 106-2, …, 106-n. Meters are often installed at user terminals, and the concentrator 104 communicates downstream 110 with the meters. The master meter station 102 can collect data from the meters and the concentrator 104 through a communication network, including real-time data and historical data, and can also perform data processing and analysis on the collected data and store the processed data in a database for subsequent query and analysis. In addition, the master meter station can manage the meters and the concentrator, including operations such as device registration, configuration, and upgrade.

[0018] As Figure 1As shown, the master meter station 102 configures a meter list at the system end according to user requirements. The meter list includes meter information (such as meter number, model, communication address, etc.) and meter tasks corresponding to the meter information. The meter tasks include task numbers and acquisition tasks corresponding to the task numbers. The meter tasks of each meter in the meter list can be configured as needed. Based on the user's acquisition requirements, different acquisition tasks can be configured. For example, for daily, monthly, and weekly acquisition of active and reactive loads, the data objects to be acquired can be configured through the OBIS curve. The OBIS curve is generally a change curve formed by data points arranged in a time series, which can be a voltage or current curve and can reflect the acquisition changes of different periods such as daily, monthly, and weekly of the measured values of the meter. In some examples, an acquisition task corresponding to a task number includes at least one OBIS curve. The master meter station 102 sends the meter list 112 to the concentrator 104. After receiving the meter list 112, the concentrator 104 returns a setting result. If it is sent to the concentrator 104 and stored successfully, it returns success; otherwise, it returns failure. Then, the master meter station 102 needs to send it to the concentrator 104 again until it is successful. Usually, when the upstream communication is good, the master meter station 102 can successfully send it to the concentrator 104. After that, the concentrator 104 sends the relevant meter tasks to the corresponding meters according to the meter information in the meter list. In the example shown in the figure, the concentrator 104 sends the relevant meter tasks, such as 114-1, 114-2,..., 114-n, to the corresponding meters 106-1, 106-2,..., 106-n based on the meter number. When the concentrator 104 successfully sends the meter task, it will receive the feedback result "Configuration successful" sent by the meter. When there is a communication problem between the concentrator 104 and the meter, or when the communication state between the concentrator 104 and the meter is good but the meter task cannot be configured on the meter, the concentrator 104 will receive the feedback result "Configuration failed" sent by the meter. In this case, the concentrator 104 responds to this feedback result and retransmits the meter task corresponding to this meter until the retransmission cycle ends, or until the configuration is successful.

[0019] In this way, after ensuring that the concentrator 104 successfully receives the meter list sent by the master meter station 102, the distribution, feedback, and retransmission are mainly carried out through the communication path between the concentrator 104 and the meter. The concentrator 104 can send the relevant meter tasks to the corresponding meters according to the meter list, and can also automatically respond to the feedback result of failure and retransmit. In this way, the concentrator 104 shares the functions previously borne by the master meter station 102, and does not require manual identification of the time period with good communication status. It can automatically respond to the situation and perform multiple retransmissions until the retransmission cycle ends or a successful feedback result is received, greatly improving the efficiency and success rate of the meter task distribution.

[0020] It should be understood that the architecture and functions in the exemplary environment 100 are described for illustrative purposes only, without implying any limitation on the scope of the present disclosure. Embodiments of the present disclosure can also be applied to other environments with different structures and / or functions.

[0021] Figure 2 FIG. 4 shows a flowchart of a meter task configuration method 200 according to some embodiments of the present disclosure. The method 200 can be executed, for example, by Figure 1 the concentrator 104 in the environment 100 shown in FIG. 1. As Figure 2 shown, at block 202, the method 200 can receive a meter list sent by a meter master station. The meter list includes meter information and meter tasks corresponding to the meter information. The meter tasks include task numbers and acquisition tasks corresponding to the task numbers. The acquisition tasks include at least one OBIS curve arranged in sequence. In some examples, the meter master station needs to send meter tasks to n meters, and the meter tasks of the n meters are configured in the form of a meter list at the meter master station. Each meter can be configured with different acquisition tasks according to user needs, and at least one OBIS curve is configured in the acquisition tasks.

[0022] At block 204, the method 200 can send the meter tasks to the corresponding meters based on the meter information. When the concentrator receives the meter list, it can parse the meter list to obtain the meter tasks corresponding to the n meters, and send the meter tasks to the meters under the corresponding meter numbers according to the meter communication addresses in the meter information. The above sending process can be sent to different meters in parallel through multiple threads, or sent to the relevant meters in batches.

[0023] At block 206, the method 200 can, in response to the feedback result returned by the meter being a failure, retransmit the relevant meter tasks to the corresponding meters based on the meter information of the meters with the feedback result of failure. In some examples, the feedback result includes a communication result and a task execution result. The task execution result mainly reflects the result of whether the meter task is successfully configured on the meter. The above results correspond to different parameters to distinguish the feedback results. For example, if the communication result returns "0", it is considered that the communication is successful; if the communication result returns "2", it is considered that the communication fails. For another example, if the task execution result returns "Set response status is successful", it is considered that the task execution is successful; if it returns "Set response status is failed", it is considered that the task execution is successful.

[0024] In this way, the concentrator can issue meter tasks according to the meter list, and respond to any one of the communication result failure and the task execution result failure, retransmit the meter tasks that cannot be successfully issued, and respond automatically and quickly to improve the issuing efficiency.

[0025] Figure 3Shows a schematic diagram of the main meter station 302, concentrator 304, and multi-terminal interaction process 300 of electric meters according to some embodiments of the present disclosure. This interaction process 300 includes forming a meter list 308 at the main meter station 302, which is formed according to user requirements. Subsequently, the main meter station 302 performs the operation of sending the meter list 310 and sends the formed meter list to the concentrator 304. The concentrator 304 receives the meter list and feeds back a successful download to the main meter station 302 (not shown in the figure in this process). The concentrator 304 sends relevant meter tasks to the corresponding electric meters according to the meter information in the meter list. For example, electric meter 1 and electric meter n (306-1 and 306-2 respectively, n is a natural number). In one example, in step 312-1, the concentrator 304 sends meter task 1 to electric meter 1. Electric meter 1 receives meter task 1 and configures it, and configures the acquisition task according to the information in meter task 1. The configuration order in the electric meter is configured according to the configuration order of the OBIS curve in the meter task. When the communication state between electric meter 1 and the concentrator 304 is good, and electric meter 1 receives and successfully configures meter task 1 (i.e., the task execution is successful), it returns a successful feedback result to the concentrator 304. The concentrator 304 records according to the feedback in the task record table (performs step 318). The task record table records meter information, task number, and the configuration status of the acquisition task. For example, the configuration status of meter task 1 can be recorded as successful in the record entry corresponding to electric meter 1. In another example, in step 312-n, the concentrator 304 sends meter task n to electric meter n, and electric meter n receives meter task n and configures it (performs step 314-n). When meter task n is not successfully downloaded, it may be that the communication state between electric meter 1 and the concentrator 304 is unstable, or the meter task is not successfully configured. Then, electric meter n feeds back a failure feedback result to the concentrator 304 (performs step 316-n). The concentrator 304 records according to the feedback in the task record table. For example, the configuration status of meter task n can be recorded as failed in the record entry corresponding to electric meter n. In some examples, the task record table also records the communication result and the task execution result. In this case, before the preset number of retransmissions ends, or before the preset retransmission period ends, the concentrator 304 responds to the failure feedback record, and in step 320-n, retransmits meter task n to electric meter n, and electric meter n configures meter task n (performs step 322-n). When the download is successful, electric meter n sends a successful feedback result to the concentrator 304 (performs step 324-n). The concentrator 304 updates the task record table (performs step 326). For example, updates the configuration status of meter task n in the record entry corresponding to electric meter n from "failed" to "successful". After the concentrator 304 completes the distribution of the meter task, it can feed back the task record table to the main meter station 302 (performs step 328). In some embodiments, after the concentrator 304 completes the preset number of retransmissions or the retransmission period ends, it feeds back the task record table to the main meter station 302.In addition, the main meter station 302 can regularly obtain the task record form from the concentrator 304.

[0026] Figure 4 FIG. shows a schematic diagram of the overall logical judgment of the retransmission process 400 according to some embodiments of the present disclosure. As Figure 4 shown, at block 402, the concentrator sends a meter task to the meter. At block 404, the concentrator receives the return result returned by the meter. The retransmission process 400 can judge the feedback result at block 406. When it is a failure, the operation of block 408 is executed to extract the communication result and the task execution result in the feedback result. At block 410, the retransmission process 400 can judge whether the communication result is a failure. If so, retransmission is performed, and the process returns to block 402 for execution. At this time, the sending process of the meter task in block 402 is the process of retransmitting the meter task with retransmission failure to the meter. During this retransmission example process, the meter tasks of the meters with communication failures with the concentrator will be retransmitted. At block 410, if the communication result is judged to be successful, it is necessary to further enter block 412 to judge whether the task execution result is a failure. The feedback result sent by the same meter includes the communication result of the communication between the meter and the concentrator, and the task execution result of the meter for the acquisition tasks under different task numbers in the meter task. When judging the task execution result at block 412, it is necessary to judge the acquisition tasks corresponding to all task numbers of this meter. If the task execution results of the acquisition tasks under all task numbers are failures, then at block 414, the acquisition tasks under all task numbers of this meter are determined as the meter tasks to be retransmitted. If the task execution results of the acquisition tasks under some task numbers are failures, then at block 414, the acquisition tasks under these task numbers of this meter are determined as the meter tasks to be retransmitted, and there is no need to retransmit the acquisition tasks under other task numbers. Correspondingly, the task record form can record the configuration status of the acquisition tasks under different task numbers in detail according to the task number and the task execution result. After determining the meter tasks to be retransmitted, the process returns to block 402 for execution. At this time, the sending process of the meter task in block 402 is the process of retransmitting the meter task with retransmission failure to the meter. The retransmission process 400 can judge whether the retransmission period has ended before retransmission. If it has ended, then block 418 feeds back the task record form to the main meter station, so that the main meter station can understand the distribution situation of the meter tasks. If the retransmission period has not ended, retransmission is performed. In one example, the concentrator is configured with a retransmission period T. The concentrator judges whether the retransmission period has ended, which can be determined based on the first sending time and the retransmission period T. When the time when retransmission is required is within the range of (the first sending time + the retransmission period T), retransmission is performed. Otherwise, it is determined that the retransmission period has ended. In another example, based on the number of retransmissions, it is judged whether the retransmission period has ended. Each time retransmission is performed, the count is incremented by one. By judging that the count value of retransmission is not greater than the retransmission times threshold, retransmission is performed. Otherwise, retransmission ends.

[0027] In some embodiments, in response to the communication result being successful and there being failed tasks in the task execution result, a new meter list is formed based on the meter information of the meters with failed task execution results and the task numbers of the failed tasks. The meter tasks in the new meter list are the meter tasks that need to be retransmitted. In some examples, the task execution result return parameters include the task number and the execution result of the acquisition task. The acquisition task is usually configured with at least one OBIS curve in sequence by the user at the meter master station end as needed. Correspondingly, the acquisition task is also configured with OBIS curves in sequence at the meter end. When the meter configuration is successful, the configuration results of the corresponding OBIS curves are fed back. Finally, the concentrator receives the OBIS feedback sequence. The OBIS feedback sequence is identified in binary form, with 0 indicating failure and 1 indicating success. For example, if there are 6 OBIS curves and all are configured successfully, the OBIS feedback sequence is [1,1,1,1,1,1]. If some of the OBIS curves are configured failed, the OBIS feedback sequence may be [1,0,1,0,1,1], [1,1,1,1,1,0], [0,1,1,1,1,1], etc. This OBIS feedback sequence can be recorded in the log of the concentrator. When there is a "0" in the OBIS feedback sequence, the execution result of the acquisition task is displayed as failed in the feedback result. When all in the OBIS feedback sequence are "1", the execution result of the acquisition task is displayed as successful in the feedback result. When the communication result is successful and there are failed tasks in the task execution result, obtain the task numbers of the failed tasks in the task execution result and obtain the OBIS feedback sequence of the task numbers of the corresponding meters from the log of the concentrator. Then, traverse the OBIS feedback sequence. When the first digit in the sequence is 0 when traversing, all the acquisition tasks of the meter with this task number need to be retransmitted. When the configuration result in the sequence is 1, traverse to the next digit. When it is recognized that the configuration result is 0 for the first time, such as the second digit in [1,0,1,0,1,1] or the sixth digit in [1,1,1,1,1,0], a new acquisition task is formed. A new meter task is formed based on this new acquisition task, and then the new meter task is retransmitted. In this way, fewer acquisition tasks can be retransmitted, and it is ensured that after retransmission, the OBIS curves in the acquisition tasks configured at the meter end are still configured according to the configuration order of the meter master station, and the meter can collect the required data and form relevant OBIS curves in sequence.

[0028] Figure 5 FIG. shows an exemplary diagram of the retransmission process according to some embodiments of the present disclosure. As Figure 5As shown, the retransmission process 500 includes a first determination unit 504 that makes a parsing determination based on the feedback result 502. When it is recognized that the communication result is a failure, the task execution result is not refined, and the meter task with a failed communication result is obtained, and then the relevant meter list 508 is obtained. For example, if the communication between the electricity meter 3 and the concentrator fails, the meter task related to the electricity meter 3 is obtained, including task numbers 01, 02, 03 and their related acquisition tasks. The above-mentioned multiple meter tasks and meter information form the meter list shown in the figure. After that, the retransmission unit 522 sends the meter task to the electricity meter 3 according to the meter list. In some examples, the meter list also contains the meter tasks of other electricity meters, and the retransmission unit 522 sends the meter tasks belonging to the same electricity meter to the relevant electricity meters.

[0029] As Figure 5As shown, the retransmission process 500 further includes a second determination unit 510. When the first determination unit 504 identifies that the communication result is successful, the second determination unit 510 further determines the task execution result. When it is determined that the communication result is successful and the task execution result is failed, the block 512 determines the meter tasks with successful communication results and failed task execution results and sends them to the acquisition unit 514. The acquisition unit 514 obtains the OBIS feedback sequence 518 corresponding to the meter information and task number of the meter task with a successful communication result and a failed task execution result from the concentrator log 516. The traversal determination unit 518 identifies the acquisition task configuration situation based on the OBIS feedback sequence, and then determines whether to perform a full retransmission or a partial retransmission. In one example, the traversal determination unit 518 processes the OBIS feedback sequence [111011] of task number 02 of meter 1. The traversal determination unit 518 sequentially traverses and identifies the values in the sequence. When the first digit is identified as "1", the next digit is traversed. When the fourth digit is traversed and is "0", the traversal ends, forming a new meter list 520-1, which includes the acquisition tasks that need to be retransmitted, OBIS24, OBIS25, and OBIS26. As for the acquisition tasks OBIS21~OBIS23, it has been determined that the configuration is successful at the meter end, so there is no need to retransmit. Based on the acquisition task where the configuration result first appears as 0, this acquisition task and subsequent acquisition tasks are formed into a new meter list. This can reduce the occupancy of retransmission resources and improve the efficiency of meter task distribution. Moreover, the acquisition tasks successfully configured at the meter end are still configured in sequence according to the user end requirements, and the meter end forms the required OBIS curve according to the sequence. In another example, the traversal determination unit 518 processes the OBIS feedback sequence [011011] of task number 01 of meter 2. The traversal determination unit 518 sequentially traverses and identifies the values in the sequence. When the first digit is identified as "0", the traversal ends, and it is determined that all acquisition tasks corresponding to task number 01 of meter 2 are retransmission acquisition tasks, and a meter list with all acquisition tasks of task number 01 of meter 2 is obtained in the block 520-2. The retransmission unit 522 performs retransmission according to the meter list sent by the traversal determination unit 518.

[0030] After the first retransmission is completed, the electricity meter feeds back the result to the concentrator. If the feedback result is a failure, the concentrator repeats the retransmission process 500 for retransmission. If it is successful, no further retransmission is performed. For example, due to the previous retransmission, the communication result and execution result corresponding to task number 02 of electricity meter 1 are both successful. In this case, the first judgment unit does not respond to the feedback result, and the concentrator updates the configuration status of the acquisition task for task 02 of electricity meter 1 in the task record table. Another example is that due to the previous retransmission, for the meter task of electricity meter 2 with task number 01 where the communication result is successful but the task execution result is a failure, the latest OBIS feedback sequence, which may be [111011], needs to be obtained from the concentrator's log. At this time, when it is recognized that the fourth digit is "0", a new meter list is formed in box 520-1, and the retransmission unit 522 performs retransmission based on the new meter list. In addition, before each retransmission, the retransmission unit 522 also needs to judge the retransmission period (see Figure 4 Example). When the time for retransmission is within the range of (the time when the meter master station first sends the meter task + retransmission period T), the meter task is continued to be retransmitted according to the determined meter list. If it is not within the above range, the retransmission unit stops the retransmission process. In this way, if it cannot be successful within a certain retransmission period, there are other problems and the reasons need to be screened manually.

[0031] In some embodiments, the retransmission process 500 further includes that after receiving the meter list sent by the traversal judgment unit 518, the retransmission unit 522 also needs to judge the retransmission times. If the retransmission times are less than the retransmission threshold, retransmission is performed according to the meter list sent by the traversal judgment unit 518. In an example, according to the meter information and the task number, the number of times the meter task under the same task number of the same meter is retransmitted is counted. If the retransmission times are less than the retransmission threshold, retransmission can continue. Generally, after the meter terminal configures the acquisition task and puts it into use, the meter will perform relevant OBIS curve acquisition according to the acquisition task. The retransmission threshold is the number threshold set according to the acquisition task executed by the meter, and is obtained by converting according to the average time required for a single retransmission (determined according to historical retransmission statistics) and the allowable configuration duration of the meter task. For example, if the acquisition task is the daily load acquisition task, the meter needs to execute the acquisition task on the second day after configuration. Then, it is necessary to calculate the allowable configuration duration of the meter task according to the first issuance time of the acquisition task and the time of 0:00 on the second day, and calculate the number of times based on the allowable configuration duration of the meter task divided by the average time required for a single retransmission (for example, determined by the floor function). When the meter master station configures the meter task, it configures the retransmission threshold according to the foregoing calculation method. When the meter master station sends the meter list to the concentrator, it also sends the retransmission threshold to the concentrator. The retransmission unit 522 of the concentrator judges the retransmission times according to the retransmission threshold. In this way, it can be ensured that the acquisition task is configured to the meter in time, and it is avoided that the meter performs acquisition for a period of time based on some previously configured acquisition tasks, and then performs acquisition for another period of time based on some later configured acquisition tasks, resulting in too long acquisition time difference for multiple acquisition tasks under the same task number and affecting the effectiveness of data acquisition.

[0032] The retransmission process 500 further includes that when the retransmission unit 522 judges that the retransmission times are not less than the retransmission threshold, it obtains the meter tasks with successful communication results and failed task execution results determined by the second judgment unit 510, performs full retransmission on the meter tasks and sends the retransmission threshold. The retransmission unit 522 also needs to clear the retransmission times of the meter tasks under the same task number of the same meter. The meter performs overwrite configuration on the received same acquisition task. The meter executes based on the latest configured acquisition task, that is, according to the latest acquisition task, the acquisition task is executed at the new execution time. After that, the meter feeds back the result to the concentrator. If the retransmission is successful, the retransmission process ends. If it fails, the first judgment unit 504 of the concentrator judges the feedback result to determine whether it is a case of failed communication result or enters the case where the second judgment unit 510 determines that the communication result is successful and the task result is failed, and then continues to perform retransmission according to the retransmission process 500 in the figure. During this period, the retransmission times of the meter tasks under the same task number of the same meter are re-counted. In addition, the retransmission unit also needs to judge the retransmission period (see Figure 4Example), when the retransmission is required within the range of (the time when the meter main station first sends the meter task + the retransmission period T), the meter task is retransmitted according to the determined meter list. If not within the above range, the retransmission unit stops the retransmission process.

[0033] Figure 6 FIG. 600 is an exemplary diagram showing a new meter list formation process according to some embodiments of the present disclosure. As Figure 6 shown, the process 600 traverses and judges based on the meter tasks with failed execution results to determine a meter list including the meter tasks that need to be retransmitted. Taking Figure 6 the execution result of task number 02 of meter 1 shown as an example of failure, the acquisition unit 606 acquires that the meter task with the failed execution result belongs to meter 1 and its task number 02. According to the meter information and the task number, the acquisition unit 606 acquires the relevant OBIS feedback sequence 608 from the concentrator's log. The sequence in the figure is [111011]. The traversal judgment unit 610 traverses and identifies the OBIS feedback sequence 608. When it is identified that the fourth bit is "0", the digit information is sent to the second processing unit 618, and the first processing unit 612 is also triggered to acquire the meter list (only the meter list 614 of meter 1 is shown in the figure by way of example. In actual application, the concentrator receives the meter tasks of multiple meters included in the meter list sent by the meter main station). The first processing unit 612 acquires the meter sub-list 616 (with 6 acquisition tasks) of task number 02 of meter 1 from the meter list 614 based on the meter number and task number of the meter task with the failed execution result. The second processing unit 618 intercepts the acquisition tasks in the meter sub-list based on the meter sub-list 616 and the digit information (such as the 4th bit), and intercepts from the 4th bit to the end, finally forming a partial meter sub-list 620 including the new retransmission meter tasks. The processed acquisition tasks in the figure include OBIS24, OBIS25, and OBIS26. In this way, it is not necessary to perform a full retransmission of the acquisition tasks under the same failed task under the same meter number. The retransmission can start from the failed configured acquisition tasks, reducing the retransmission resource occupancy and improving the retransmission efficiency of the downlink communication. In some examples, if the first bit in the OBIS feedback sequence with the failed execution result is "0", the meter sub-list 616 output by the first processing unit 612 and the partial meter sub-list 620 output by the second processing unit 618 are the same. Figure 6 Only the formation process of the meter list that needs to be retransmitted is described by way of example. In fact, the meter list contains more and more complex information, such as meter tasks including multiple meter numbers, and there may be meter tasks under different task numbers under each meter number. By performing the acquisition task interception process on each row in the meter list, a partial meter sub-list 620 with a smaller data volume can be finally formed, realizing a more efficient and targeted retransmission, and greatly improving the distribution efficiency and retransmission efficiency of the meter tasks.

[0034] Figure 7 FIG. shows an exemplary schematic diagram of the supplementary transmission task formation process 700 according to some embodiments of the present disclosure. In some embodiments, when the electricity meter and the concentrator are in a negotiation state, the concentrator has not received the feedback of successful configuration of the electricity meter. There is an incomplete OBIS feedback sequence in the concentrator's log. By determining that the feedback time after issuing the meter task to the electricity meter exceeds the threshold time, and determining that the number of feedback values in the OBIS feedback sequence related to the relevant electricity meter and task is less than the number of OBIS curves under the task number related to the electricity meter, it is determined that the electricity meter and the concentrator are negotiating and waiting for configuration. Taking the OBIS feedback sequence of task number 02 of electricity meter 1 as an example, when the concentrator determines that the electricity meter feedback time has timed out, it obtains the relevant OBIS feedback sequence

[111] in the log, identifies that there are 3 feedback values in the OBIS feedback sequence, and correspondingly obtains the number of acquisition tasks of the corresponding electricity meter and task number in the meter list issued by the master station of the electricity meter to the concentrator. For example, there are 6 acquisition tasks, including OBIS21 to OBIS26. When the feedback value 3 is less than the acquisition task number 6, it is determined that there is a problem of negotiation and waiting for configuration in the acquisition task configuration of the electricity meter for task number 02. Among them, OBIS21 to OBIS23 are successfully configured, while the configuration of OBIS24 is in the waiting stage, and the subsequently configured OBIS25 and OBIS26 cannot enter the configuration because OBIS24 is in the waiting configuration stage. In this case, the concentrator may be unable to successfully configure the meter task to the electricity meter due to too many retransmissions and occupying the communication. Therefore, the process 700 can confirm this meter task as a supplementary transmission task, reduce the amount of data retransmitted in the current retransmission process, and perform supplementary transmission separately after the retransmission cycle ends.

[0035] Such as Figure 7As shown, the process 700 includes block 704 that determines whether the feedback time exceeds a threshold time, and block 706 that determines whether the number of values in the OBIS feedback sequence is less than the number of OBIS curves. Herein, the threshold time is the time when the concentrator receives the OBIS feedback sequence from the electricity meter under normal communication conditions. The feedback time is determined by calculating the difference between the concentrator transmission time and the judgment time. When both block 704 and block 706 are yes, at block 708, the meter task corresponding to the OBIS feedback sequence is determined as a retransmission task. For example, based on the acquisition tasks OBIS21 - OBIS26 with task number 02, a retransmission task is formed. Then, at block 710, the retransmission task and the corresponding electricity meter information are stored in the retransmission list. After the concentrator sends the meter tasks to the electricity meters according to the meter list of the meter master station, it starts to irregularly detect the feedback time of the electricity meters and processes the process 700. When retransmission is required, after the concentrator's corresponding feedback result is a failure and retransmission is performed, the concentrator needs to record the retransmission time and the retransmission feedback time, and process the process 700 for each retransmission process. In this way, during retransmission, the retransmission list is continuously updated. Through this process judgment, the data that needs to enter retransmission can be shunted, mainly for the situation where normal configuration can be achieved but the communication channel may not meet the configuration requirements, which not only improves the retransmission efficiency but also enhances the retransmission success rate. At block 712, it is judged that the retransmission cycle ends, and at block 714, based on the retransmission list, the concentrator sends the retransmission task to the corresponding electricity meter.

[0036] In some embodiments, after the concentrator distributes the retransmission task to the relevant electricity meters based on the retransmission list, the concentrator receives the feedback result from the electricity meters. The concentrator updates the task record table according to the feedback result. In one example, if the feedback result is successful, under the corresponding electricity meter information and task number in the task record table, the configuration status of the acquisition task is updated from failure to success. In another example, if the feedback result is a failure, an exception handling message is sent to the meter master station, and the meter master station initiates a manual inspection process, such as sending an exception handling message to the mobile terminal, and the maintenance personnel conduct a manual inspection of the exception.

[0037] Figure 8The structural block diagram of a meter task configuration system 800 according to some embodiments of the present disclosure is shown. The system 800 includes a meter master station 810, a concentrator 820, and a plurality of electric meters 830-1, 830-2, …, 830-n. The meter master station 810 is used to form a meter list based on meter task update information. The meter task update information is configured by the user according to requirements, including meter information, task objects (such as data), collection tasks (such as OBIS curves), collection periods, configuration methods (such as sending to tables), etc. The meter master station 810 includes a template module 813. For example, the templates include a daily load collection template, a monthly load collection template, a freeze template, etc. The template module 813 determines the template to be used according to the meter task update information 812 and outputs a task template 814 to the task module 815. The task module 815 configures information such as task names, collection tasks, collection periods, and configuration methods based on the task template 814. The task module 815 generates a task number based on the task serial number 816, and generates a meter task by combining the task number with the information configured by the task module. In some embodiments, the task module 815 needs to obtain an unoccupied task number based on the task serial number and the task record table of the concentrator, that is, the configuration status corresponding to the task number in the task record table is in the state of being configured or the configuration is not completed. The task template 815 forms a meter task based on the task template and the unoccupied task number. If an unoccupied task number cannot be obtained and an error message "${terminal number} The current task is full, please try again later" is returned, it is necessary to wait until the task configuration is completed and the task number is released, that is, the configuration status corresponding to the task number in the task record table is in the state of successful configuration or configuration completion. Generally, the available range of the task number is 1-64, and when the same task number is sent, the concentrator performs an overwrite process. As Figure 8 shown, the meter master station 810 further includes a list module 819, which is used to form a meter list based on the meter information and meter tasks in the meter task update information and send it to the concentrator 820.

[0038] As Figure 8As shown, the concentrator 820 includes a receiving module 828 for receiving the meter list sent by the meter master station and the feedback results returned by the meters. When the receiving module 828 receives the meter list, it sends it to the distribution module 826. The distribution module 826, based on the meter information, sends meter tasks to the corresponding meters 830-1, 830-2, …, 830-n. After the meters 830-1, 830-2, …, 830-n are configured with the meter tasks, they send the feedback results to the receiving module 828. The receiving module 828 records the configuration status (including success and failure) of the meter tasks in the task record table 824 based on the feedback results. The receiving module 828 sends the meter tasks with failed feedback results and the meter information to the retransmission module 829. The retransmission module 829 is used to retransmit the relevant meter tasks to the corresponding meters during the retransmission period in response to the feedback results returned by the meters being failed, based on the meter information of the meters with failed feedback results. The meters 830-1, 830-2, …, 830-n are configured according to the retransmitted meter tasks and return the feedback results to the receiving module 828 of the concentrator 820. The receiving module 828 will update the task record table 824 based on the feedback results and also send the ones with failed feedback results to the retransmission module 829. The retransmission module 829 retransmits the meter tasks within the retransmission period and stops retransmitting after the retransmission period ends. The concentrator 820 further includes an upload module 822 for uploading the task record table recorded during the retransmission period to the task module 815 of the meter master station 810. The task module 815 can obtain the task record table 824 and determine the unoccupied task numbers. The task module 815 can also save the task record table 824 to the database.

[0039] Figure 9 FIG. shows a schematic diagram of a task template configuration interface 900 of a meter master station according to some embodiments of the present disclosure. As Figure 9 shown, after determining the task template, the task template configuration interface 900 configures the collection task, configuration method, collection period, etc. On the right side of the interface 900 is the collection task selection directory. When the user checks the OBIS curve, the configuration of the collection task can be completed on the left side. By setting the configuration method to "distribute to the meter", the meter task can be sent to the terminal meter through the concentrator. The collection period of the concentrator, the meter collection time, and the interval time can also be configured on the left side of the interface 900. After the configuration is completed, a meter task can be formed.

[0040] Figure 10 FIG. shows a schematic diagram of a meter list configuration process 1000 according to some embodiments of the present disclosure. As Figure 10As shown, the process 1000 can perform task group creation 1002, specifically creating task group details through window 1004, including electricity meter information, configuration methods, task objects, etc. Different types of meter tasks can be configured within the task group, and the task types are determined by the selected task templates 1006-1, …, 1006-n. The task module and list module of the electricity meter master station (see Figure 8 the reference numerals 815, 818 in the attached drawing) form meter tasks according to the task templates and Figure 9 the configured task information, and attribute the meter tasks to the created task group, then the meter list 1010 can be output. The meter list exemplified in the figure includes task groups of the test type for electricity meter 1 and other types of task groups for electricity meter 1, as well as task groups of the test type for electricity meter 2, etc., where each task group contains one or more meter tasks of its own. In some embodiments, instead of creating a task group, meter lists are generated based on the meter tasks formed according to the task templates and electricity meter information.

[0041] Figure 11 The block diagram of an electronic device 1100 that can implement multiple embodiments of the present disclosure is shown. As Figure 11 shown, the device 1100 includes a processor 1101, which can execute various appropriate actions and processes according to computer program instructions stored in a read-only memory (ROM) 1102 and loaded into a random access memory (RAM) 1103. In the RAM 1103, various programs and data required for the operation of the device 1100 can also be stored. The processor 1101, ROM 1102, and RAM 1103 are connected to each other through a bus 1104. An input / output (I / O) interface 1105 is also connected to the bus 1104.

[0042] The various processes and processes described above, such as method 200, can be executed by the processor 1101. For example, in some embodiments, method 200 can be implemented as a software program that is tangibly included in a machine-readable medium. In some embodiments, part or all of the software program can be loaded and / or installed onto the device 1100 via the ROM 1102. When the software program is loaded into the RAM 1103 and executed by the processor 1101, one or more actions of the method 200 described above can be performed.

[0043] The functions described above herein can be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that can be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on a chip (SOCs), complex programmable logic devices (CPLDs), and so on.

[0044] The program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the program codes cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on the machine, partially on the machine, executed partially on the machine and partially on a remote machine as an independent software package, or executed entirely on a remote machine or server.

[0045] The present disclosure may be a method, apparatus, system, and / or program product. The program product may include a machine-readable storage medium having machine-readable program instructions thereon for performing various aspects of the present disclosure. The machine-readable program instructions described herein may be downloaded from the machine-readable storage medium to various computing / processing devices, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network may include copper transmission cables, optical fiber transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter or network interface in each computing / processing device receives the machine-readable program instructions from the network and forwards the machine-readable program instructions for storage in the machine-readable storage medium in each computing / processing device.

[0046] The machine program instructions for performing the operations of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages such as Smalltalk, C++, etc., and conventional procedural programming languages such as the "C" language or similar programming languages. The machine-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or executed entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, by using the state information of the machine-readable program instructions to customize an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), the electronic circuit may execute the machine-readable program instructions to implement various aspects of the present disclosure.

[0047] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. Additionally, although the operations are depicted in a particular order, this should be understood to require that the operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed to achieve the desired result. In certain environments, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single implementation. Conversely, the various features that are described in the context of a single implementation can also be implemented separately or in any suitable sub-combination in multiple implementations.

[0048] Although the subject matter has been described in language specific to structural features and / or methodological acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims.

Claims

1. A method for configuring meter tasks, which is executed on a concentrator, characterized in that, Including: Receiving a meter list sent by a master meter station, the meter list including meter information and meter tasks corresponding to the meter information, the meter tasks including task numbers and acquisition tasks corresponding to the task numbers, and the acquisition tasks including at least one OBIS curve arranged in sequence; Based on the meter information, sending the meter tasks to the corresponding meters; And In response to the feedback result returned by the meter being a failure, based on the meter information of the meter with the feedback result failure, retransmitting the relevant meter tasks to the corresponding meters.

2. The method according to claim 1, characterized in that, In response to the feedback result returned by the meter being a failure, based on the meter information of the meter with the feedback result failure, retransmitting the relevant meter tasks to the corresponding meters includes: In response to the feedback result returned by the meter being a failure, extracting the communication result and task execution result in the feedback result; In response to the communication result being a failure, based on the meter information of the meter with the communication result failure, retransmitting the relevant meter tasks to the corresponding meters; In response to the communication result being successful and there being failed tasks in the task execution result, based on the meter information of the meter with the task execution result failure and the task numbers of the failed tasks, retransmitting the relevant meter tasks to the corresponding meters.

3. The method according to claim 2, wherein In response to the communication result being successful and there being failed tasks in the task execution result, based on the meter information of the meter with the task execution result failure and the task numbers of the failed tasks, retransmitting the relevant meter tasks to the corresponding meters includes: In response to the communication result being successful and there being failed tasks in the task execution result, obtaining the task numbers of the failed tasks and the OBIS feedback sequence in the task execution result, the OBIS feedback sequence storing the configuration results of the OBIS curves according to the configuration order in the acquisition task, identifying failure with binary 0 and success with binary 1; and Traversing the OBIS feedback sequence in sequence, in response to the configuration result being 0 for the first time in the OBIS feedback sequence, based on the meter information of the meter with the task execution result failure, the task numbers of the failed tasks, and the OBIS curves corresponding to the OBIS feedback sequence from the first occurrence of the configuration result being 0 to the end of the sequence in the acquisition task, determining the retransmission meter tasks; based on the meter information of the meter with the task execution result failure, retransmitting the retransmission meter tasks to the corresponding meters.

4. The method according to claim 2, characterized in that In response to the communication result being successful and there being failed tasks in the task execution result, based on the meter information of the meter with the task execution result failure and the task numbers of the failed tasks, retransmitting the relevant meter tasks to the corresponding meters includes: In response to the communication result being successful and there being failed tasks in the task execution result, obtaining the task numbers of the failed tasks and the OBIS feedback sequence in the task execution result, the OBIS feedback sequence storing the configuration results of the OBIS curves according to the configuration order in the acquisition task, identifying failure with binary 0 and success with binary 1; and In response to the first occurrence of a configuration result of 0 in the OBIS feedback sequence and the number of retransmissions being less than the retransmission threshold, determine a retransmission meter task based on the meter information of the meter with a failed task execution result, the task number of the failed task, and the OBIS curve corresponding to the OBIS feedback sequence from the first occurrence of a configuration result of 0 to the end of the sequence in the acquisition task; based on the meter information of the meter with a failed task execution result, retransmit the retransmission meter task to the corresponding meter; and in response to the first occurrence of a configuration result of 0 in the OBIS feedback sequence and the number of retransmissions being not less than the retransmission threshold, retransmit the relevant meter task to the corresponding meter based on the meter information of the meter with a failed task execution result and the task number of the failed task.

5. The method according to claim 4, wherein In response to the first occurrence of a configuration result of 0 in the OBIS feedback sequence and the number of retransmissions being not less than the retransmission threshold, retransmitting the relevant meter task to the corresponding meter based on the meter information of the meter with a failed task execution result and the task number of the failed task includes: In response to the first occurrence of a configuration result of 0 in the OBIS feedback sequence and the number of retransmissions being not less than the retransmission threshold, and in response to the retransmission period not ending, retransmit the relevant meter task to the corresponding meter based on the meter information of the meter with a failed task execution result and the task number of the failed task, clear the number of retransmissions, and return to the feedback result response step; In response to the first occurrence of a configuration result of 0 in the OBIS feedback sequence and the number of retransmissions being not less than the retransmission threshold, and in response to the retransmission period ending, end the retransmission.

6. The method according to claim 3 or 4, characterized in that, Determining a retransmission meter task based on the meter information of the meter with a failed task execution result, the task number of the failed task, and the OBIS curve corresponding to the OBIS feedback sequence from the first occurrence of a configuration result of 0 to the end of the sequence in the acquisition task includes: Based on the meter information of the meter with a failed task execution result and the task number of the failed task, obtain the meter sub-list corresponding to the task number under this meter from the meter list; Based on the order of the first occurrence of a configuration result of 0 in the OBIS feedback sequence, intercept the acquisition tasks in the meter sub-list from this order to the end to obtain a partial meter sub-list containing the retransmission meter task.

7. The method according to claim 3 or 4, characterized in that The method further includes: In response to the number of values in the OBIS feedback sequence being less than the number of OBIS curves under the task number related to the corresponding meter and the feedback time exceeding the threshold time, form a supplementary transmission task from the acquisition tasks under the task number related to the OBIS feedback sequence, and store the supplementary transmission task and the meter information in a supplementary transmission list in correspondence; After the retransmission period ends, send the supplementary transmission task to the corresponding meter based on the meter information in the supplementary transmission list.

8. A meter task configuration system, comprising a main meter station, a concentrator, and a plurality of electric meters; characterized in that, The meter master station is used to form a meter list based on the meter task update information, and the meter master station is also used to send the meter list to the concentrator, and the concentrator configures the meter task for the meter based on the meter task configuration method according to any one of claims 1 to 7.

9. The system according to claim 8, wherein The meter master station includes: A template module, configured to form a task template based on the task object, acquisition object, acquisition period, and configuration method of the meter task update information; A task module, configured to obtain an unoccupied task number based on a task serial number and a task record table of the concentrator, and form the meter task based on the task template and the unoccupied task number, wherein the task record table records meter information and the configuration status of the acquisition task corresponding to the meter information; A list module, configured to form the meter list based on the meter information of the meter task update information and the meter task.

10. The system according to claim 8, wherein The concentrator includes: A receiving module, configured to receive the meter list sent by the meter master station and the feedback result returned by the meter; A sending module, configured to send the meter task to the corresponding meter based on the meter information; A retransmission module, configured to, during the retransmission period, in response to the feedback result returned by the meter being a failure, retransmit the relevant meter task to the corresponding meter based on the meter information of the meter with the feedback result being a failure; An uploading module, configured to upload the task record table recorded during the retransmission period to the meter master station, wherein the task record table records meter information and the configuration status of the acquisition task corresponding to the meter information.

Images