Metering task configuration method and system

Abstract

The embodiment of the present disclosure discloses a meter task configuration method and system. The method includes receiving a meter list sent by an electric meter master station, the meter list including electric meter information and a meter task corresponding to the electric meter information, the meter task including a task number and an acquisition task corresponding to the task number, and the acquisition task including at least one OBIS curve arranged in sequence. The method also includes sending the meter task to the corresponding electric meter based on the electric meter information. In addition, the method also includes, in response to the feedback result returned by the electric meter being a failure, retransmitting the relevant meter task to the corresponding electric meter based on the electric meter information of the electric meter with the failed feedback result. In this way, the electric meter master station sends the meter list to the electric meter through the concentrator, and can retransmit and send it in response to the failure result by the concentrator, which not only shortens the sending and receiving feedback path, improves the efficiency of meter task sending, but also reduces the resource occupation of the electric meter master station, and does not affect the operation of other functions of the master station.

Description

Technical Field

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

[0002] Typically, a master meter station distributes metering tasks to terminal meters via a concentrator. The terminal meters then perform data collection tasks based on the metering tasks. If downlink communication between the concentrator and the meters is poor, metering tasks cannot be successfully distributed. The master meter station must resend the tasks multiple times until all metering tasks are successfully distributed. This consumes significant resources at the master station and may even impact the execution of other tasks. Furthermore, the long retransmission and feedback paths prolong distribution and feedback times, and introduce significant communication instability, reducing the efficiency of metering task distribution. Summary of the Invention

[0003] One or more embodiments of the present disclosure describe a meter task configuration method and system, aiming to solve one or more of the above-mentioned problems and other potential problems.

[0004] In a first aspect of the present disclosure, a method for configuring meter tasks is provided. The method includes receiving a meter list transmitted from an electric meter master station, the meter list including electric meter information and meter tasks corresponding to the electric meter information, the meter tasks including task numbers and collection tasks corresponding to the task numbers, the collection tasks including at least one sequentially arranged OBIS curve. The method also includes transmitting the meter tasks to corresponding electric meters based on the electric meter information. Furthermore, the method also includes, in response to a feedback result returned by the electric meter indicating a failure, retransmitting the relevant meter tasks to the corresponding electric meter based on the electric meter information of the electric meter with the failure feedback result.

[0005] In a second aspect of the present disclosure, a meter task configuration system is provided. The system includes an electric meter master station, a concentrator, and multiple electric meters. The electric meter master station is configured to generate a meter list based on meter task update information. The electric meter master station is further configured to send the meter list to the concentrator, which then configures meter tasks for the electric meters based on the method described in the first aspect.

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

[0007] In a fourth aspect of the present disclosure, a machine-readable storage medium is provided, wherein the machine-readable storage medium stores machine-executable instructions, wherein the machine-executable instructions are executed by a processor to implement the method provided according to the first aspect of the present disclosure.

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

[0009] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0010] Figure 1 A schematic diagram illustrating an example environment in which some embodiments of the present disclosure may be implemented;

[0011] Figure 2 A flow chart of a meter task configuration method according to some embodiments of the present disclosure is shown;

[0012] Figure 3 A schematic diagram showing a multi-terminal interaction process among an electric meter master station, a concentrator, and an electric meter according to some embodiments of the present disclosure is shown;

[0013] Figure 4 A schematic diagram of overall logic judgment of a retransmission process according to some embodiments of the present disclosure is shown;

[0014] Figure 5 An exemplary schematic diagram illustrating a retransmission process according to some embodiments of the present disclosure is shown;

[0015] Figure 6 An exemplary schematic diagram illustrating a new meter list forming process according to some embodiments of the present disclosure is shown;

[0016] Figure 7 An exemplary schematic diagram illustrating a process of forming a supplementary transmission task according to some embodiments of the present disclosure is shown;

[0017] Figure 8 A structural block diagram of a meter task configuration system according to some embodiments of the present disclosure is shown;

[0018] Figure 9 A schematic diagram illustrating a task template configuration interface of an electric meter master station according to some embodiments of the present disclosure is shown;

[0019] Figure 10 A schematic diagram illustrating a meter list configuration process according to some embodiments of the present disclosure; and

[0020] Figure 11 A block diagram of an electronic device in which various embodiments of the present disclosure may be implemented is shown. DETAILED DESCRIPTION

[0021] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying 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 described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0022] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to." The term "based on" should be understood as "based at least in part 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. Other explicit and implicit definitions may also be included below.

[0023] Typically, electricity meters are configured with relevant metering tasks based on factory task templates before leaving the factory. These tasks include energy metering (including active energy metering, reactive energy metering, time-of-use metering, and tiered electricity pricing), parameter configuration (including meter operating parameters), data collection and storage (including real-time data collection, historical data storage, and frozen data), and status monitoring and fault diagnosis (including meter operating status monitoring, fault detection, and abnormality alarms). When meters are put into operation, they often require customized configuration based on the varying needs of end users.

[0024] When a meter master station assigns metering tasks to end-user meters, it often transmits them to the end-user meters via a concentrator using transparent transmission. In this transparent transmission mode, the concentrator acts merely as a data relay, forwarding the received data intact to the end-user meters. Uplink communication between the meter master station and the concentrator is typically achieved using GPRS or Ethernet, and communication is generally excellent. Downlink communication between the concentrator and the meters is typically achieved using G3-PLC (third-generation power line communication) or BPLC (broadband power line communication). However, due to complex field environments, various factors such as impedance, attenuation, and noise can cause periodic communication problems. For example, turning on LED streetlights introduces significant noise, preventing PLC communication during the on-time period. The task success rate during this period is almost zero, forcing operations to be performed at other times. For delivery sites with tens of thousands of meters, manually selecting time slots for re-operation is time-consuming and labor-intensive, resulting in ineffective results. During this process, the long dispatch and feedback paths, coupled with unstable downlink communications, result in prolonged meter task dispatching, low dispatch efficiency, and a high dispatch failure rate. While reissuing meter tasks at alternate times can mitigate communication failures to some extent, each reissuance relies on the meter master station. With tens of thousands of dispatch objects and information to be dispatched, the master station must maintain high operational capacity, significantly impacting the normal operation of other meter master station functions. Furthermore, during the meter task dispatching process, downlink communications can be good, but the meter task configuration at the terminal meter fails. Based on this feedback, the meter master station must re-issuance the meter task for configuration. Due to occasional poor communication and random configuration failures during meter task dispatching, the existing dispatching communication model results in low efficiency and a low success rate for meter task dispatching and re-issuing.

[0025] To this end, embodiments of the present disclosure propose a meter task configuration method that can configure meter tasks issued by a meter master station on a concentrator, primarily relying on the concentrator to deliver the meter tasks to corresponding terminal meters. Even in the event of feedback failures, such as poor communication or configuration failures, the concentrator can automatically respond and resend the failed meter tasks to the corresponding terminal meters.

[0026] In this way, the concentrator receives metering tasks configured by the meter master station and, acting as both the sender and retransmitter, distributes these tasks to tens of thousands of terminal meters. This not only reduces the meter master station's resource usage, ensuring it can handle other functions such as metering task configuration and meter status monitoring, but also shortens the delivery and feedback paths, improving delivery and retransmission efficiency. Furthermore, it allows for more frequent delivery of metering tasks within a given period, increasing the delivery success rate.

[0027] Figure 1 1 shows a schematic diagram of an example environment 100 in which some embodiments of the present disclosure may be implemented. Figure 1 As shown, environment 100 includes an electricity meter master station 102, which is typically a core system used by power systems to centrally manage and control electricity meter data. It typically runs on a server or computer cluster, which requires powerful computing and storage capabilities to handle large amounts of data and concurrent tasks. Environment 100 also includes a concentrator 104, which communicates uplink 108 with the electricity meter master station 102, typically via 2G / 3G / 4G / 5G. Environment 100 also includes multiple electricity meters 106-1, 106-2, ..., 106-n. The electricity meters are often located at user terminals, with downlink communication 110 between the concentrator 104 and the meters. The electricity meter master station 102 can collect data from the electricity meters and concentrator 104 via a communication network, including real-time and historical data. It can also process and analyze the collected data and store the processed data in a database for subsequent query and analysis. In addition, the meter master station can manage meters and concentrators, including equipment registration, configuration, and upgrades.

[0028] like Figure 1As shown, the meter master station 102 configures a meter list on the system side based on user needs. This meter list includes meter information (such as meter number, model, and mailing address) and meter tasks corresponding to this meter information. A meter task includes a task number and a corresponding collection task. Meter tasks for each meter in the meter list can be configured as needed. Based on user collection requirements, different collection tasks can be configured, such as collecting active and reactive loads on a daily, monthly, or weekly basis. The collected data objects can be configured using OBIS curves. OBIS curves are generally based on a time-series curve of data points, such as voltage or current curves, that reflects changes in meter measurement values ​​over different periods, such as daily, monthly, and weekly. In some examples, a task number corresponds to a collection task containing at least one OBIS curve. The meter master station 102 sends the meter list 112 to the concentrator 104. After receiving the meter list 112, the concentrator 104 returns the configuration result. If the configuration has been successfully sent to the concentrator 104 and stored, it indicates success. Otherwise, it indicates failure. The meter master station 102 must send the configuration to the concentrator 104 again until success is achieved. Typically, if uplink communication is good, the meter master station 102 can successfully send the configuration to the concentrator 104. The concentrator 104 then sends the relevant meter tasks to the corresponding meters based on the meter information in the meter list. In the example shown, the concentrator 104 sends the corresponding meter tasks (e.g., 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 tasks, it receives feedback from the meters indicating "Configuration Successful." If there is a communication problem between the concentrator 104 and the meter, or if communication between the concentrator 104 and the meter is good but the meter task cannot be configured on the meter, the concentrator 104 will receive a "configuration failed" response from the meter. In this case, the concentrator 104 responds to this response by retransmitting the meter task for the meter until the retransmission period ends or until configuration is successful.

[0029] In this way, after ensuring that the concentrator 104 successfully receives the meter list sent by the meter master station 102, it primarily distributes, feedbacks, and retransmits tasks via the communication path between the concentrator 104 and the meters. The concentrator 104 can distribute relevant meter tasks to the corresponding meters based on the meter list and automatically respond to feedback failures by retransmitting tasks. This offloads the functions previously performed by the meter master station 102 and eliminates the need for manual identification of periods of good communication. Instead, the concentrator 104 can automatically respond to these conditions and retransmit tasks multiple times until the retransmission cycle ends or successful feedback is received, significantly improving the efficiency and success rate of meter task distribution.

[0030] It should be understood that the purpose of describing the architecture and functions in the example environment 100 is only exemplary and does not imply any limitation on the scope of the present disclosure. The embodiments of the present disclosure can also be applied to other environments with different structures and / or functions.

[0031] Figure 2 FIG. 1 shows a flow chart of a meter task configuration method 200 according to some embodiments of the present disclosure. The method 200 may be, for example, Figure 1 The concentrator 104 in the illustrated environment 100 performs the following. Figure 2 As shown, at block 202, method 200 may receive a meter list sent by an electricity meter master station. The meter list includes meter information and meter tasks corresponding to the meter information. The meter tasks include task numbers and corresponding collection tasks. The collection tasks include at least one sequentially arranged OBIS curve. In some examples, the electricity meter master station needs to send meter tasks to n electricity meters, and the meter tasks for these n electricity meters are configured at the electricity meter master station in the form of a meter list. Each electricity meter can be configured with a different collection task based on user needs, and each collection task is configured with at least one OBIS curve.

[0032] At block 204, method 200 can send metering tasks to corresponding meters based on the meter information. After receiving the meter list, the concentrator can parse the list to obtain metering tasks corresponding to n meters. Based on the meter communication addresses in the meter information, the metering tasks can be sent to the meters with the corresponding meter numbers. This sending process can be performed in parallel using multiple threads to send tasks to different meters, or in batches.

[0033] In box 206, method 200 can retransmit the relevant metering task to the corresponding meter in response to the feedback result returned by the meter being a failure, based on the meter information of the meter whose feedback result failed. In some examples, the feedback result includes the communication result and the task execution result. The task execution result mainly reflects whether the metering 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, and if the communication result returns "2", it is considered that the communication failed. For another example, if the task execution result returns "Set response status is success", it is considered that the task execution is successful, and if it returns "Set response status is failure", it is considered that the task execution is successful.

[0034] In this way, the concentrator can issue metering tasks according to the meter list, and respond to any of the communication failures and task execution failures, retransmitting metering tasks that failed to be successfully issued, automatically responding quickly and improving the issuance efficiency.

[0035] Figure 3A schematic diagram illustrates a multi-terminal interaction process 300 among a master meter station 302, a concentrator 304, and electricity meters, according to some embodiments of the present disclosure. This interaction process 300 includes forming a meter list 308 at the master meter station 302, which is generated based on user requirements. The master meter station 302 then performs a meter list transmission 310, sending the generated meter list to the concentrator 304. The concentrator 304 receives the meter list and sends a successful transmission notification to the master meter station 302 (this process is not shown in the figure). Based on the meter information in the meter list, the concentrator 304 sends the relevant meter tasks to the corresponding meters, for example, meter 1 and meter n (306-1 and 306-2, respectively, where n is a natural number). In one example, in step 312-1, the concentrator 304 sends meter task 1 to electricity meter 1. Meter 1 receives meter task 1 and configures it. It configures the collection task based on the information in meter task 1, with the configuration order within the meter following the order of the OBIS curves in the meter task. If communication between meter 1 and the concentrator 304 is good, meter 1 receives meter task 1 and successfully configures it (i.e., the task is successfully executed), and then returns a successful feedback result to the concentrator 304. The concentrator 304 records this feedback in a task record table (proceeding to step 318). The task record table records the meter information, task number, and collection task configuration status. For example, the record entry corresponding to meter 1 may record that the configuration status of meter task 1 is successful. In another example, in step 312-n, the concentrator 304 sends meter task n to electricity meter n. Meter n receives meter task n and configures it (proceeding to step 314-n). If meter task n is not successfully delivered, this could be due to unstable communication between meter 1 and concentrator 304, or the meter task configuration was unsuccessful. In this case, meter n then provides a failure feedback result to concentrator 304 (step 316-n). Concentrator 304 records the feedback in a task record table. For example, the entry corresponding to meter n may record the configuration status of meter task n as "failed." In some examples, the task record table also records the communication results and task execution results. In this case, before a preset number of retransmissions or a preset retransmission period expires, concentrator 304 responds to the failure feedback record by retransmitting meter task n to meter n in step 320-n, and meter n configures meter task n (step 322-n). If the delivery is successful, meter n sends a success feedback result to concentrator 304 (step 324-n). Concentrator 304 updates the task record table (step 326). For example, the configuration status of meter task n in the record entry corresponding to meter n is updated from "failed" to "successful." After the concentrator 304 completes the meter task delivery, it can feed the task record table back to the meter master station 302 (perform step 328). In some embodiments, the concentrator 304 feeds the task record table back to the meter master station 302 after completing a preset number of retransmissions or after a retransmission cycle has expired.In addition, the electric meter master station 302 may periodically obtain the task record table from the concentrator 304 .

[0036] Figure 4 FIG. 4 shows a schematic diagram of the overall logic judgment of the retransmission process 400 according to some embodiments of the present disclosure. Figure 4 As shown, in block 402, the concentrator sends a metering task to the electricity meter. In block 404, the concentrator receives the response from the electricity meter. The retransmission process 400 can determine the feedback result in block 406. If it fails, block 408 is executed to extract the communication result and task execution result from the feedback result. In block 410, the retransmission process 400 can determine whether the communication result fails. If so, the task is retransmitted and the process returns to block 402. In this case, the metering task transmission process in block 402 retransmits the failed metering task to the electricity meter. In this retransmission example, the metering task for the meter that failed to communicate with the concentrator is retransmitted. If the communication result is determined to be successful in block 410, the process proceeds to block 412 to determine whether the task execution result fails. The feedback result sent by the same electricity meter includes the communication result between the meter and the concentrator, as well as the task execution results of the meter for the collection tasks with different task numbers within the metering task. When determining the task execution results in block 412, the collection tasks corresponding to all task numbers for the meter are evaluated. If all collection tasks with task numbers fail, then block 414 identifies all collection tasks with task numbers for the meter as retransmitted meter tasks. If some collection tasks with task numbers fail, then block 414 identifies these tasks as retransmitted meter tasks, while the collection tasks with other task numbers do not need to be retransmitted. Accordingly, the task record table can record the configuration status of the collection tasks with different task numbers in detail based on the task number and the task execution results. After determining the retransmitted meter tasks, the process returns to block 402. At this point, the meter task transmission process in block 402 is the process for retransmitting failed meter tasks to the meter. The retransmission process 400 can determine whether the retransmission cycle has ended before retransmission. If so, block 418 sends the task record table back to the meter master station, allowing the meter master station to understand the meter task delivery status. If the retransmission period has not ended, a retransmission is performed. In one example, the concentrator is configured with a retransmission period T. The concentrator determines whether the retransmission period has ended based on the initial transmission time and the retransmission period T. If the required retransmission time is within the range of (initial transmission time + retransmission period T), retransmission is performed; otherwise, the retransmission period is considered to have ended. In another example, the end of the retransmission period is determined based on the number of retransmissions. Each retransmission increments a count. If the retransmission count does not exceed a retransmission threshold, retransmission is performed; otherwise, retransmission is terminated.

[0037] In some embodiments, in response to a successful communication result and a task that failed during task execution, a new meter list is created based on the meter information of the meter with the failed task execution result and the task number of the failed task. The meter tasks in this new meter list are the meter tasks that need to be retransmitted. In some examples, the task execution result return parameter includes the task number and the execution result of the collection task. The collection task is typically configured by the user at the meter master station in sequence according to needs, with at least one OBIS curve. Accordingly, the collection task also sequentially configures OBIS curves at the meter. If the meter configuration is successful, the configuration result will be fed back for each OBIS curve. Ultimately, the concentrator receives the OBIS feedback sequence. The OBIS feedback sequence is represented in binary form, with 0 indicating failure and 1 indicating success. For example, if there are six OBIS curves and all are configured successfully, the OBIS feedback sequence is [1,1,1,1,1,1]. If some OBIS curves fail to configure, the OBIS feedback sequence may be [1,0,1,0,1,1], [1,1,1,1,1,1,0], [0,1,1,1,1,1,1], and so on. This OBIS feedback sequence can be recorded in the concentrator's log. If there is a "0" in the OBIS feedback sequence, the feedback result indicates that the collection task has failed. If all OBIS feedback sequences are "1," the feedback result indicates that the collection task has succeeded. If the communication result is successful and there are failed tasks in the task execution results, the task number of the failed task is obtained from the task execution results and the OBIS feedback sequence for the corresponding meter task number is obtained from the concentrator's log. Next, the OBIS feedback sequence is traversed. When the first bit in the sequence is 0, all collection tasks for that task number of the meter need to be retransmitted. If the configuration result in the sequence is 1, the next bit is traversed. When the first occurrence of a configuration result of 0 is detected, such as the second bit in [1,0,1,0,1,1] or the sixth bit in [1,1,1,1,1,0], a new collection task is formed. Based on this new collection task, a new metering task is formed, and the new metering task is retransmitted. This method can retransmit fewer collection tasks and ensure that after retransmission, the OBIS curves in the collection tasks configured at the meter end are still configured according to the configuration order of the meter master station. The meter can collect the required data and form the relevant OBIS curves in sequence.

[0038] Figure 5 FIG. 1 shows an exemplary schematic diagram of a retransmission process according to some embodiments of the present disclosure. Figure 5As shown, the retransmission process 500 includes a first judgment unit 504 analyzing and judging the feedback result 502. If the communication result is determined to be a failure, the task execution result is not further refined, and the meter tasks for which the communication result failed are obtained, followed by a list of related meters 508. For example, if meter 3 fails to communicate with the concentrator, meter tasks related to meter 3 are obtained, including task numbers 01, 02, and 03, as well as their associated collection tasks. These multiple meter tasks and meter information form the meter list shown in the figure. Subsequently, the retransmission unit 522 sends the meter tasks to meter 3 based on the meter list. In some examples, the meter list also contains meter tasks for other meters, and the retransmission unit 522 sends the meter tasks belonging to the same meter to the relevant meters.

[0039] like Figure 5As shown, the retransmission process 500 also includes a second determination unit 510. When the first determination unit 504 identifies a successful communication result, the second determination unit 510 further determines the task execution result. If the communication result is successful and the task execution result is unsuccessful, block 512 identifies the meter tasks for which the communication result is successful and the task execution result is unsuccessful and sends the results to the acquisition unit 514. Based on the meter information and task number of the meter tasks for which the communication result is successful and the task execution result is unsuccessful, the acquisition unit 514 retrieves the OBIS feedback sequence 518 corresponding to the meter and task number from the concentrator log 516. The traversal determination unit 518 identifies the collection task configuration based on the OBIS feedback sequence and determines whether to perform a full or partial retransmission. In one example, the traversal determination unit 518 processes the OBIS feedback sequence [111011] for 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 traversal is performed on the next digit. When the fourth bit is "0", the traversal ends and a new meter list 520-1 is formed. The meter list includes the collection tasks that need to be retransmitted, OBIS24, OBIS25, and OBIS26. As for the collection tasks OBIS21~OBIS23, it has been determined that the configuration is successful on the meter side, so there is no need to retransmit. Based on the collection task with the configuration result of 0 appearing for the first time, this collection task and subsequent collection tasks are formed into a new meter list. This can reduce the retransmission resource usage and improve the efficiency of meter task distribution. In addition, the collection tasks successfully configured on the meter side are still configured in sequence according to the needs of the user side, and the meter side forms the required OBIS curve according to the sequence. In another example, the traversal judgment unit 518 processes the OBIS feedback sequence [011011] of task number 01 of meter 2. Traversal determination unit 518 sequentially traverses and identifies the values ​​in the sequence. When the first value is identified as "0," traversal ends, and all collection tasks corresponding to task number 01 of electricity meter 2 are determined to be retransmission collection tasks. At block 520-2, a list of meters with all collection tasks corresponding to task number 01 of electricity meter 2 is obtained. Retransmission unit 522 performs retransmission based on the meter list sent by traversal determination unit 518.

[0040] After one retransmission is completed, the 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 retransmission is performed. For example, due to the previous retransmission, the communication result and execution result corresponding to the task number 02 of meter 1 are both successful. In this way, the first judgment unit does not respond to the feedback result, and the concentrator updates the configuration status of the collection task of the task 02 of meter 1 in the task record table. For another example, due to the previous retransmission, the task number 01 of meter 2 still has a meter task with a successful communication result and a failed task execution result. In this case, it is necessary to obtain the latest OBIS feedback sequence from the concentrator's log, which may be [111011]. At this time, when the fourth bit is recognized as "0", a new meter list is formed in box 520-1, and the retransmission unit 522 retransmits 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 For example, if the retransmission time is within the range of (the time the meter master station first sends the meter task + the retransmission period T), the meter task will continue to be retransmitted according to the specified meter list. If it is not within this range, the retransmission unit stops the retransmission process. If the retransmission fails within a certain retransmission period, other problems may exist and manual investigation is required.

[0041] In some embodiments, the retransmission process 500 further includes the retransmission unit 522 determining the number of retransmissions after receiving the meter list sent by the traversal determination unit 518. If the number of retransmissions is less than a retransmission threshold, retransmission is performed according to the meter list sent by the traversal determination unit 518. In one example, the number of retransmissions for the same meter task with the same task number for the same meter is counted based on the meter information and task number. If the number of retransmissions is less than the retransmission threshold, retransmissions can continue. Generally, after a collection task is configured and put into use, the meter will perform relevant OBIS curve collection according to the collection task. The retransmission threshold is a threshold value set according to the number of times the meter executes the collection task. It is calculated based on the average time required for a single retransmission (determined based on historical retransmission statistics) and the allowed configuration time of the meter task. For example, if the collection task is a daily load collection task, and the meter needs to execute the collection task the day after configuration, the meter task's allowed configuration duration is calculated based on the time the collection task was first issued and midnight the next day. The number of retransmissions is then calculated (e.g., using rounding down) by dividing the allowed configuration duration by the average time required for a single retransmission. When configuring the meter task, the meter master station configures the retransmission threshold based on the aforementioned calculation method. When the meter master station sends the meter list to the concentrator, it also sends the retransmission threshold to the concentrator. The concentrator's retransmission unit 522 determines the number of retransmissions based on the retransmission threshold. This ensures that the collection task is assigned to the meter in a timely manner, preventing the meter from performing collection for a period based on a previously configured collection task and then performing collection for another period based on a later configured collection task. This would result in a significant difference in the collection times between multiple collection tasks under the same task number, impacting the effectiveness of data collection.

[0042] The retransmission process 500 also includes the retransmission unit 522, when determining that the number of retransmissions is not less than a retransmission threshold, obtaining the meter task for which the second determination unit 510 determined that the communication result was successful and the task execution result was failed, retransmitting the meter task in full, and sending the retransmission threshold. The retransmission unit 522 also clears the retransmission count for all meter tasks with the same task number for the same meter. The meter overwrites the received identical collection tasks and executes them based on the most recently configured collection task, i.e., executing the collection task at the new execution time according to the most recently configured collection task. The meter then feeds back the result to the concentrator. If the retransmission is successful, the retransmission process ends. If it fails, the concentrator's first determination unit 504 evaluates the feedback result to determine whether the communication result failed or whether the second determination unit 510 determines that the communication result was successful and the task result failed, and then continues the retransmission process according to the retransmission process 500 shown in the figure. During this period, the number of retransmissions for the meter task with the same task number for the same meter is re-counted. In addition, the retransmission unit also needs to determine the retransmission period (see Figure 4For example), when the retransmission time is within the range of (the time when the meter master station first sends the meter task + the retransmission period T), the meter task will continue to be retransmitted according to the determined meter list. If it is not within the above range, the retransmission unit stops the retransmission process.

[0043] Figure 6 FIG. 6 is an exemplary diagram showing a new meter list forming process 600 according to some embodiments of the present disclosure. Figure 6 As shown, the process 600 performs traversal judgment based on the meter tasks whose execution results fail to determine the meter list containing the meter tasks that need to be retransmitted. Figure 6 Taking the example of the failed execution result of task number 02 of meter 1, acquisition unit 606 determines that the meter task with the failed execution result belongs to meter 1 and its task number 02. Based on the meter information and task number, acquisition unit 606 retrieves the relevant OBIS feedback sequence 608 from the concentrator log, which is [111011]. Traversal determination unit 610 traverses and identifies OBIS feedback sequence 608. When the fourth bit is identified as "0," it sends the bit number information to second processing unit 618 and triggers first processing unit 612 to obtain a meter list (meter list 614 for meter 1 is shown as an example only; in actual applications, the concentrator receives meter tasks for multiple meters in a meter list sent from the meter master station). Based on the meter number and task number of the meter task with the failed execution result, first processing unit 612 retrieves a meter sublist 616 (containing six collection tasks) for task number 02 of meter 1 from meter list 614. Based on meter sublist 616 and the bit information (e.g., the 4th bit), second processing unit 618 truncates the collection tasks in the meter sublist, starting from the 4th bit and ending at the end, ultimately forming a partial meter sublist 620 containing newly retransmitted meter tasks. The processed collection tasks shown in the figure include OBIS24, OBIS25, and OBIS26. This eliminates the need to fully retransmit all collection tasks under the same table number and the same failed task. Retransmission can begin with the failed configured collection task, reducing retransmission resource usage and improving retransmission efficiency for downlink communications. In some examples, if the first bit in the OBIS feedback sequence for a failed execution result is "0," meter sublist 616 output by first processing unit 612 and partial meter sublist 620 output by second processing unit 618 are identical. Figure 6 This example illustrates the process of generating a meter list requiring retransmission. In reality, a meter list can contain more complex information, such as meter tasks with multiple meter numbers, each of which may have different task numbers. By performing collection task interception processing on each row in the meter list, a partial meter sub-list 620 with less data can be generated, enabling more efficient and targeted retransmission, significantly improving the efficiency of meter task issuance and retransmission.

[0044] Figure 7 An exemplary schematic diagram of the supplementary transmission task formation process 700 according to some embodiments of the present disclosure is shown. In some embodiments, when the meter and the concentrator are in a negotiation state, the concentrator has not received any feedback on the successful configuration of the meter, and there is an incomplete OBIS feedback sequence in the log of the concentrator. The concentrator determines that the meter and the concentrator are negotiating and waiting for configuration by judging that the feedback time after the meter task is sent to the meter exceeds the threshold time, and judging that the number of feedback values ​​in the OBIS feedback sequence under the relevant meter and task is less than the number of OBIS curves under the task number related to the meter. Taking the OBIS feedback sequence of task number 02 of meter 1 as an example, the concentrator obtains the relevant OBIS feedback sequence

[111] in the log after judging that the meter feedback time has timed out, identifies that there are 3 feedback values ​​in the OBIS feedback sequence, and accordingly obtains the number of collection tasks under the corresponding meter and task number in the meter list sent to the concentrator by the meter master station, such as 6 collection tasks, including OBIS21~OBIS26. If the feedback value 3 is less than the number of collection tasks 6, the meter's collection task configuration for task number 02 is determined to be in a negotiation waiting configuration phase. OBIS21 through OBIS23 are successfully configured, while OBIS24 is in the waiting phase. Furthermore, the later configured OBIS25 and OBIS26 are unable to proceed with configuration because OBIS24 is in the waiting configuration phase. In this case, the concentrator may be unable to successfully configure the meter task due to excessive retransmissions, which consume communication resources. Therefore, process 700 can identify this meter task as a supplementary transmission task, reducing the amount of retransmitted data in the current retransmission process. After the retransmission period ends, a separate supplementary transmission is performed.

[0045] like Figure 7As shown, process 700 includes block 704, determining whether the feedback time exceeds a threshold time, and block 706, determining whether the number of values ​​in the OBIS feedback sequence is less than the number of OBIS curves. The threshold time is the time it takes for the concentrator to receive the OBIS feedback sequence from the meter under normal communication conditions. The feedback time is determined by calculating the difference between the concentrator's transmission time and the determination time. If both blocks 704 and 706 are true, block 708 determines the meter task corresponding to the OBIS feedback sequence as a supplementary transmission task. For example, based on collection tasks OBIS21-OBIS26 with task number 02, a supplementary transmission task is generated. Next, block 710 stores the supplementary transmission task and the corresponding meter information in a supplementary transmission list. After the concentrator sends the meter task to the meter according to the meter list from the meter master station, it begins periodically checking the meter's feedback time and proceeding with process 700. When retransmission is required, the concentrator responds with a failure response and then retransmits. The concentrator records the retransmission time and retransmission feedback time, and performs process 700 for each retransmission. This process continuously updates the retransmission list during the retransmission period. This process allows for the diversion of data requiring retransmission, primarily for data that can be configured normally but may not meet the configuration requirements due to the communication channel. This not only improves retransmission efficiency but also increases the retransmission success rate. At block 712, the retransmission cycle is determined to have ended. At block 714, the concentrator sends a retransmission task to the corresponding electricity meter based on the retransmission list.

[0046] In some implementations, the concentrator issues a retransmission task to the relevant meter based on the retransmission list and then receives feedback from the meter. Based on the feedback, the concentrator updates the task record table. In one example, if the feedback result is success, the configuration status of the collection task is updated from failure to success under the corresponding meter information and task number in the task record table. In another example, if the feedback result is failure, an exception handling message is sent to the meter master station, which then initiates a manual inspection process, such as sending the exception handling message to a mobile device for maintenance personnel to manually inspect the anomaly.

[0047] Figure 8The block diagram shows a structure of a meter task configuration system 800 according to some embodiments of the present disclosure. System 800 includes a meter master station 810, a concentrator 820, and multiple meters 830-1, 830-2, ..., 830-n. The meter master station 810 is used to generate a meter list based on meter task update information. This meter task update information is configured by the user based on user needs and includes meter information, task objects (e.g., data), collection tasks (e.g., OBIS curves), collection cycles, and configuration methods (e.g., sending to meters). The meter master station 810 includes a template module 813. Templates include, for example, daily load collection templates, monthly load collection templates, and frozen templates. Template module 813 determines the template to use based on meter task update information 812 and outputs a task template 814 to a task module 815. Task module 815 configures information such as the task name, collection task, collection cycle, and configuration method based on task template 814. The task module 815 generates a task number based on the task serial number 816, and generates a metering 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 metering task based on the task template and the unoccupied task number. If an unoccupied task number cannot be obtained, an error message "${terminal number} The current task is full, please try again later" is returned. It is necessary to wait for the task configuration to be completed and the task number to be 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 task numbers is 1-64. When the same task number is issued, the concentrator takes overwriting processing. For example Figure 8 As shown, the electric meter master station 810 further includes a list module 819 for forming a meter list based on the electric meter information and the meter tasks in the meter task update information and sending the list to the concentrator 820 .

[0048] like Figure 8As shown, the concentrator 820 includes a receiving module 828 for receiving a meter list sent by the meter master station and feedback results returned by the meters. After receiving the meter list, the receiving module 828 sends it to the sending module 826. Based on the meter information, the sending module 826 sends meter tasks to the corresponding meters 830-1, 830-2, ..., 830-n. After configuring the meter tasks, the meters 830-1, 830-2, ..., 830-n send feedback results to the receiving module 828. Based on the feedback results, the receiving module 828 records the configuration status (including success or failure) of the meter tasks in the task record table 824. The receiving module 828 sends meter tasks with a failed feedback result and meter information to the retransmission module 829. The retransmission module 829 is configured to retransmit the relevant meter tasks to the corresponding meters during the retransmission period in response to feedback results indicating failure from the meters, based on the meter information of the meters with failed feedback results. Tables 830-1, 830-2, ..., 830-n are configured based on the retransmitted metering tasks and feedback results are returned to the receiving module 828 of the concentrator 820. The receiving module 828 updates the task record table 824 based on the feedback results and sends any failed feedback results to the retransmission module 829. The retransmission module 829 retransmits metering tasks within the retransmission period and ceases retransmission after the retransmission period ends. The concentrator 820 also 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 retrieves the task record table 824 and determines the unoccupied task number. The task module 815 also saves the task record table 824 in a database.

[0049] Figure 9 FIG. 1 shows a schematic diagram of a task template configuration interface 900 of an electric meter master station according to some embodiments of the present disclosure. Figure 9 As shown, after selecting a task template, the task template configuration interface 900 is used to configure the collection task, configuration method, and collection period. The right side of interface 900 displays the collection task selection directory. After selecting the OBIS curve, the user completes the collection task configuration on the left side. By selecting the "Distribute to meter" configuration method, the meter task is sent to the terminal meter via the concentrator. The left side of interface 900 also allows configuration of the concentrator collection period, meter collection time, and interval. Once the configuration is complete, the meter task is created.

[0050] Figure 10 FIG. 1 is a schematic diagram illustrating a meter list configuration process 1000 according to some embodiments of the present disclosure. Figure 10As shown, the process 1000 can proceed to create a task group 1002. Specifically, the task group details are created through window 1004, including meter information, configuration method, task objects, etc. Different task types can be configured in the task group. The task type is determined by the selected task template 1006-1, ..., 1006-n. The task module and list module of the meter master station (see Figure 8 815, 818) according to the task template and Figure 9 The configured task information is used to form meter tasks, which are then assigned to the created task groups. A meter list 1010 can then be output. The example meter list in the figure includes a test-type task group for meter 1, a task group for other types of meter 1, and a task group for test-type meter 2, each of which contains one or more meter tasks. In some implementations, task groups are not created, and a meter list is generated based on the meter tasks and meter information generated by the task template.

[0051] Figure 11 1 shows a block diagram of an electronic device 1100 that can implement various embodiments of the present disclosure. Figure 11 As shown, device 1100 includes a processor 1101, which can perform 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. RAM 1103 may also store various programs and data required for the operation of device 1100. Processor 1101, ROM 1102, and RAM 1103 are connected to each other via a bus 1104. An input / output (I / O) interface 1105 is also connected to bus 1104.

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

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

[0054] The program code for implementing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when the program code is executed by the processor or controller, the functions / operations specified in the flow chart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0055] The present disclosure may be a method, apparatus, system and / or program product. The program product may include a machine-readable storage medium on which are loaded machine-readable program instructions for executing various aspects of the present disclosure. The machine-readable program instructions described herein may be downloaded from the machine-readable storage medium to each computing / processing device, 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. The network adapter card 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.

[0056] 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++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The machine-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or 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 via 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, the state information of the machine-readable program instructions is used to personalize an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), so that the electronic circuit can execute the machine-readable program instructions, thereby implementing various aspects of the present disclosure.

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

[0058] Although the subject matter has been described in language specific to structural features and / or methodological logical 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 meter task configuration method, executed in a concentrator, characterized in that: include: receiving a meter list sent by an electric meter master station, the meter list including electric meter information and a meter task corresponding to the electric meter information, the meter task including a task number and a collection task corresponding to the task number, the collection task including at least one OBIS curve arranged in sequence; Based on the electricity meter information, sending the meter task to the corresponding electricity meter; as well as In response to a feedback result returned by the electric meter indicating failure, retransmitting the relevant metering task to the corresponding electric meter based on the electric meter information of the electric meter with the failed feedback result, including: In response to a feedback result returned by the electric meter being a failure, extracting a communication result and a task execution result from the feedback result; In response to a communication failure, retransmitting the relevant metering task to the corresponding meter based on the meter information of the meter with the failed communication result; In response to a successful communication result and a failed task in the task execution result, the task number and OBIS feedback sequence of the failed task in the task execution result are obtained, the OBIS feedback sequence stores the configuration results of the OBIS curve according to the configuration order in the acquisition task, and uses binary 0 to identify failure and binary 1 to identify success; in response to the first appearance of the configuration result of 0 in the OBIS feedback sequence and the number of retransmissions is less than the retransmission threshold, based on the meter information of the meter with failed task execution results, the task number of the failed task, and the OBIS curve in the acquisition task corresponding to the first appearance of the configuration result of 0 in the OBIS feedback sequence to the end of the sequence, the retransmitted meter task is determined; based on the meter information of the meter with failed task execution results, the retransmitted meter task is retransmitted to the corresponding meter; and in response to the first appearance of the configuration result of 0 in the OBIS feedback sequence and the number of retransmissions is not less than the retransmission threshold, the relevant meter task is retransmitted to the corresponding meter based on the meter information of the meter with failed task execution results and the task number of the failed task.

2. The method according to claim 1, characterized in that 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 a retransmission threshold, retransmitting the relevant metering task to the corresponding meter based on the meter information of the meter for which the task execution result failed 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, based on the meter information of the meter that failed the task execution result and the task number of the failed task, retransmitting the relevant metering task to the corresponding meter, resetting the number of retransmissions to 0, and returning to the feedback result response step; In response to the configuration result being 0 appearing for the first time 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, the retransmission is terminated.

3. The method according to claim 1, characterized in that Based on the meter information of the meter that failed task execution, the task number of the failed task, and the OBIS curve corresponding to the first occurrence of the configuration result of 0 in the OBIS feedback sequence in the collection task to the end of the sequence, the retransmission meter task is determined as follows: Based on the meter information of the meter that failed the task execution result and the task number of the failed task, obtaining a meter sub-list corresponding to the task number under the meter from the meter list; Based on the order in which the configuration result 0 first appears in the OBIS feedback sequence, the collection tasks in the meter sublist are intercepted from the order to the end to obtain a partial meter sublist containing retransmission meter tasks.

4. The method according to claim 1, wherein The method also 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 associated with the corresponding electric meter and the feedback time exceeding the threshold time, the collection task under the task number associated with the OBIS feedback sequence is constituted as a supplementary transmission task, and the supplementary transmission task is stored in a supplementary transmission list in correspondence with the electric meter information; After the retransmission period ends, the supplementary transmission task is sent to the corresponding electricity meter based on the electricity meter information in the supplementary transmission list.

5. A meter task configuration system, comprising an electric meter master 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 meter task update information. The meter master station is also used to send the meter list to the concentrator. The concentrator configures meter tasks for the meters based on any meter task configuration method in claims 1 to 4.

6. The system according to claim 5, characterized in that The electric meter master station includes: A template module, configured to form a task template based on the task object, collection object, collection cycle, 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 to form the meter task based on the task template and the unoccupied task number, wherein the task record table records meter information and a configuration status of a collection task corresponding to the meter information; A list module is used to form the meter list based on the meter information of the meter task update information and the meter task.

7. The system according to claim 5, characterized in that The concentrator includes: The receiving module is used to receive the meter list sent by the meter master station and the feedback results returned by the meter; A sending module, configured to send the metering task to the corresponding meter based on the meter information; a retransmission module, configured to, in response to a feedback result returned by the electric meter being a failure during a retransmission period, retransmit the relevant metering task to the corresponding electric meter based on the electric meter information of the electric meter having the feedback result being a failure; The uploading module is used to upload the task record table recorded in the retransmission period to the electric meter master station, wherein the task record table records the electric meter information and the configuration status of the collection task corresponding to the electric meter information.

Images