Method and apparatus for pushing metering data, device, and medium

Abstract

Embodiments of the present application disclose a metering data pushing method and device, electronic equipment and computer readable medium, wherein the method comprises the following steps: receiving a target metering data pushing strategy sent by a controller; wherein the target metering data pushing strategy is a strategy matched with an application scene category and determined by the controller according to a detected current application scene category, and metering data pushing strategies corresponding to different application scene categories are different; obtaining actual metering working parameters; and pushing metering data obtained by metering to the controller according to a relationship between the actual metering working parameters and metering configuration working parameters corresponding to the target metering data pushing strategy. Through the method, the flexibility of metering data pushing can be improved.

Description

Technical Field

[0001] This application relates to the field of electronic technology, and more specifically, to a method for pushing measurement data, a device for pushing measurement data, an electronic device, and a computer-readable medium. Background Technology

[0002] A water and gas meter is a battery-powered metering product consisting of a mainboard and a metering unit. This product can meet the functional requirements of displaying water and gas usage data, calculating costs, and calibrating errors. To achieve these functions, the mainboard needs to obtain the latest metering data in a timely manner.

[0003] The traditional implementation method involves the motherboard and metering unit communicating via a data transfer mechanism. The motherboard initiates communication, and the metering unit receives the command and returns the corresponding data. The metering unit outputs metering data to the motherboard at a fixed period, and the motherboard updates and displays the metering data at the same period for relevant personnel to read. However, the fixed update period of the metering unit's metering data can affect the real-time performance of the data updates.

[0004] Therefore, improving the flexibility of metering data delivery is an urgent problem to be solved. Summary of the Invention

[0005] The embodiments of this application provide a method and apparatus for pushing measurement data, an electronic device, and a computer-readable medium, which can improve the flexibility of pushing measurement data.

[0006] In a first aspect, embodiments of this application provide a method for pushing metering data, including:

[0007] The system receives a target metering data push strategy sent by the control party; wherein the target metering data push strategy is a strategy determined by the control party based on the detected current application scenario category and matched with the application scenario category, and different application scenario categories correspond to different metering data push strategies.

[0008] Obtain actual measurement parameters;

[0009] Based on the relationship between the actual metering operating parameters and the metering configuration operating parameters corresponding to the target metering data push strategy, the metering data obtained by the metering is pushed to the control party.

[0010] In one embodiment of this application, based on the aforementioned scheme, the current metering stage is detected, and push conditions matching the metering stage are determined according to the detected metering stage; the metering data obtained from metering is pushed to the control party according to the relationship between the actual metering working parameters and the metering configuration working parameters and the push conditions.

[0011] In one embodiment of this application, based on the aforementioned scheme, the actual metering working parameters include metering duration, which is obtained by statistically analyzing the time period corresponding to the period when the value of the metering data does not change, and the metering configuration working parameters include a first configuration duration threshold, which is used to characterize the time period threshold when the value of the metering data does not change.

[0012] In one embodiment of this application, based on the aforementioned scheme, if the metering duration reaches the first configured duration threshold, and a change in the metering data value is detected for the first time after the metering data value has not changed, then it is determined that the current stage is the initial metering stage; if the metering duration does not reach the first configured duration threshold, then it is determined that the current stage is the continuous metering stage.

[0013] In one embodiment of this application, based on the foregoing scheme, the actual metering working parameters further include metering data increment, and the metering configuration working parameters further include a second configuration duration threshold and a configuration increment threshold. The second configuration duration threshold is used to characterize the time interval at which metering data should be pushed, and the configuration increment threshold is used to characterize the increment that the pushed metering data should reach. If the current stage is the initial metering stage, the push condition is determined to be that the metering duration reaches the second configuration duration threshold, or the metering data increment reaches the configuration increment threshold, or the metering duration reaches the second configuration duration threshold and the metering data increment reaches the configuration increment threshold. If the current stage is the continuous metering stage, the push condition is determined to be that the metering duration reaches the second configuration duration threshold and the metering data increment reaches the configuration increment threshold.

[0014] In one embodiment of this application, based on the aforementioned scheme, the metering configuration operating parameters include abnormal events; the abnormal event is detected according to the actual metering operating parameters; wherein the abnormal event includes at least one of an overcurrent event and a magnetic interference event; if an abnormal event is detected, the metering data obtained by the metering is pushed to the control party.

[0015] In one embodiment of this application, based on the aforementioned scheme, the actual metering operating parameters include metering data increments, and the metering configuration operating parameters include anomaly detection duration; the anomaly detection duration is the duration used to detect the anomaly event; the metering data change rate is calculated based on the metering data increments and the anomaly detection duration; if the metering data change rate is greater than the safe change rate, then the overcurrent event is determined to have occurred; if, within the anomaly detection duration, the change in the metering data and / or the metering data increments satisfy the magnetic interference change condition, then the magnetic interference event is determined to have occurred.

[0016] In one embodiment of this application, based on the foregoing scheme, the target metering data push strategy includes the metering configuration working parameters; the metering configuration working parameters are obtained from the target metering data push strategy; and the metering data obtained by metering is pushed to the control party according to the relationship between the actual metering working parameters and the obtained metering configuration working parameters.

[0017] In one embodiment of this application, based on the aforementioned scheme, the metering configuration working parameters corresponding to the target metering data push strategy are searched from a designated storage area; wherein, the designated storage area stores multiple metering data push strategies and metering configuration working parameters corresponding to the multiple metering data push strategies respectively; and the metering data obtained by metering is pushed to the control party according to the relationship between the actual metering working parameters and the obtained metering configuration working parameters.

[0018] Secondly, embodiments of this application provide a method for pushing measurement data, including:

[0019] Detect the current application scenario category;

[0020] Based on the detected application scenario category, a target metering data push strategy matching the application scenario category is determined; wherein, different application scenario categories correspond to different metering data push strategies;

[0021] The target metering data push strategy is sent to the metering party so that the metering party can push the metering data obtained by metering to the control party based on the relationship between the actual metering working parameters and the metering configuration working parameters corresponding to the target metering data push strategy.

[0022] Receive the measurement data sent by the measurement party.

[0023] In one embodiment of this application, based on the aforementioned scheme, before detecting the current application scenario category, a configuration instruction for each application scenario category is received, the configuration instruction including multiple metering configuration working parameters; each application scenario category is associated with the corresponding multiple metering configuration working parameters to obtain the metering data push strategy corresponding to each application scenario category.

[0024] Thirdly, embodiments of this application provide a device for pushing metering data, including:

[0025] The transceiver unit is used to receive the target metering data push strategy sent by the controller; wherein, the target metering data push strategy is a strategy determined by the controller based on the detected current application scenario category and matched with the application scenario category, and the metering data push strategy is different for different application scenario categories.

[0026] Acquisition unit, used to acquire actual measurement working parameters;

[0027] The transceiver unit is also used to push the metering data obtained from the metering to the control party based on the relationship between the actual metering working parameters and the metering configuration working parameters corresponding to the target metering data push strategy.

[0028] Fourthly, embodiments of this application provide a device for pushing metering data, including:

[0029] The detection unit is used to detect the current application scenario category;

[0030] The processing unit is used to determine a target metering data push strategy that matches the detected application scenario category; wherein, the metering data push strategy is different for different application scenario categories.

[0031] The transceiver unit is used to send the target metering data push strategy to the metering party, so that the metering party can push the metering data obtained by metering to the control party according to the relationship between the actual metering working parameters and the metering configuration working parameters corresponding to the target metering data push strategy.

[0032] The transceiver unit is also used to receive the metering data sent by the metering party.

[0033] Fifthly, embodiments of this application provide an electronic device, including one or more processors; and a memory for storing one or more programs, which, when executed by the one or more processors, enable the electronic device to implement the metering data push method described above.

[0034] Sixthly, embodiments of this application provide a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the metering data push method described above.

[0035] In a seventh aspect, embodiments of this application provide a computer program product, including computer instructions, which, when executed by a processor, implement the metering data push method described above.

[0036] In the technical solutions provided by the embodiments of this application:

[0037] The metering provider can receive a target metering data push strategy sent by the control provider. This target metering data push strategy is determined by the control provider based on the detected current application scenario category, and different application scenario categories correspond to different metering data push strategies. Different metering data push strategies have different metering configuration parameters. The metering provider can compare these parameters with the actual metering parameters and determine whether to push the obtained metering data to the control provider based on this relationship. Through this method, the metering data push strategy corresponds to the application scenario category, thus the metering data pushed by the metering provider corresponds to the application scenario category, thereby improving the metering provider's flexibility in metering data push.

[0038] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0039] Figure 1 This is a schematic diagram of the structure of an intelligent metering device that can be applied to the embodiments of this application;

[0040] Figure 2 This is a flowchart illustrating a method for pushing measurement data, as shown in an exemplary embodiment of this application;

[0041] Figure 3 This is a flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application;

[0042] Figure 4 This is a flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application;

[0043] Figure 5 This is a flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application;

[0044] Figure 6 This is a flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application;

[0045] Figure 7 This is a flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application;

[0046] Figure 8 This is a flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application;

[0047] Figure 9 This is a flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application;

[0048] Figure 10This is a flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application;

[0049] Figure 11 This is a flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application;

[0050] Figure 12 This is a block diagram of a metering data push device according to an embodiment of this application;

[0051] Figure 13 This is a schematic diagram of the structure of a computer system suitable for implementing the electronic devices of the present application embodiments. Detailed Implementation

[0052] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0053] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0054] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0055] It should also be noted that "multiple" as mentioned in this application refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0056] The methods, apparatuses, electronic devices, and computer-readable media for pushing metering data proposed in this application relate to the field of computer security technology. These embodiments will be described in detail below.

[0057] Please see Figure 1 , Figure 1This is a schematic diagram of the structure of an intelligent metering device according to this application. The intelligent metering device may include a controller 110, a metering unit 120, a display module 130, and a balance detection module 140. The controller 110 may be a base meter MCU (Micro Controller Unit), and the metering unit 120 may be a metering MCU. The display module 130 may include a lighting module 131 and a display unit 132, wherein the lighting module 131 may be an LED (light-emitting diode) lamp, and the display unit 132 may be an LCD (Liquid Crystal Display). The balance detection module 140 can be used to detect the user's remaining balance on the metered object. The metered object refers to the object being metered by the intelligent metering device, which may be water, gas, etc.

[0058] Optionally, the balance detection module 140 may be an NFC (Near Field Communication) module, which can read the user's usage balance for the metered object in NFC-enabled magnetic cards or mobile devices.

[0059] Optionally, the balance detection module 140 may be a wireless communication module that can connect to a network to obtain the user's usage balance for the metered object from a specific cloud database.

[0060] Optionally, the balance detection module 140 can be a combination of an NFC module and a wireless communication module.

[0061] In this embodiment, the controller 110 can also be referred to as the motherboard, and the metering unit 120 can also be referred to as the metering unit. For ease of description, unless otherwise specified, they are referred to as the controller and the metering unit, and are not limited thereto. Furthermore, the controller 110 can send data to the metering unit 120's Rx port via the Tx port, and correspondingly, the metering unit 120 can send data to the controller 110's Rx port via the Tx port. Further, the metering unit 120 can control the controller 110 via the Ctrl1 port, and the controller 110 can control the metering unit 120 via the Ctrl2 port. The display module 130 is connected to the controller 110, and the balance detection module 140 is also connected to the controller 110.

[0062] In this embodiment, the communication method between the controller 110 and the metering entity 120 can be UART (Universal Asynchronous Receiver / Transmitter), SPI (Serial Peripheral Interface), etc., and the communication protocol can be AT (Attention) commands, publicly available standard protocols, or proprietary protocols, etc. This embodiment does not limit the specific communication method.

[0063] Optionally, the controller 110 and the metering unit 120 may be laid out on the same circuit board, or they may be laid out on two separate circuit boards and connected by wires. This application embodiment does not limit the specific layout of the controller 110 and the metering unit 120.

[0064] In this embodiment, the controller 110, the metering unit 120, and the display module 130 can jointly form an intelligent metering device, which can also be called a water / gas meter, smart meter, etc. This intelligent metering device can be a smart gas meter, a smart water meter, etc., and can be applied to metering scenarios for different objects; this embodiment does not limit its application.

[0065] Figure 2 This is a flowchart illustrating a method for pushing metering data according to an exemplary embodiment. Figure 2 As shown, in an exemplary embodiment, the method may include steps S210 to S240, and the execution entity of this application embodiment may be as follows: Figure 1 The measurement method 120 is shown. Steps S210 to S240 are described in detail below:

[0066] Step S210: Receive the target metering data push strategy sent by the controller; wherein, the target metering data push strategy is a strategy determined by the controller based on the detected current application scenario category and matched with the application scenario category, and the metering data push strategy is different for different application scenario categories.

[0067] The target metering data push strategy corresponds to metering configuration parameters, which may include a first configuration duration threshold, a second configuration duration threshold, and a configuration increment threshold. The first configuration duration threshold represents a time period during which the metering data value remains unchanged; the second configuration duration threshold represents the time interval at which metering data should be pushed; and the configuration increment threshold represents the increment in the pushed metering data. In this embodiment, the first configuration duration threshold can be denoted as T1, the second configuration duration threshold as T2, and the configuration increment threshold as V.

[0068] The application scenario categories in this application embodiment may include meter calibration scenarios, normal usage scenarios, meter boundary value estimation scenarios, and abnormal event scenarios. Among them, normal usage scenarios can be further divided into normal usage scenarios with the display unit turned on and normal usage scenarios with the display unit turned off.

[0069] In this embodiment, the metering data push strategy differs for different application scenario categories; therefore, the metering configuration parameters also differ for different application scenario categories. In other words, T1, T2, and V may differ under different application scenario categories, and the values ​​of T1, T2, and V under different application scenarios can be designed by those skilled in the art. If those skilled in the art need to add application scenario categories, they can create a new set of T1, T2, and V values ​​to obtain new application scenario categories.

[0070] In this embodiment of the application, although both the normal use scenario with the display unit turned on and the normal use scenario with the display unit turned off are normal use scenarios, the corresponding metering configuration working parameters are different.

[0071] The application scenarios involved in the embodiments of this application are described in detail below:

[0072] (1) Calibration Scenario: In this scenario, the measurement data needs to be refreshed at a relatively fast speed, and the display unit of the smart metering device needs to display the changes in the measurement data in real time. Furthermore, in this calibration scenario, the smart metering device needs to illuminate an indicator light every time the measurement data (which can be the volume) increases by V, making it easier for the user to identify and compare the measurement data. For example, in this calibration scenario, T1 = 5s, T2 = 2s, and V = 1000mL can be set.

[0073] (2) Normal usage scenarios:

[0074] Normal usage scenario when the display unit is not turned on: If the user does not turn on the display unit, the metering data can be recorded and stored internally. In this case, there is no immediate requirement, and the metering data can be refreshed during viewing or settlement. Refreshing can be done at relatively long intervals, thus reducing the power consumption of the smart metering device. For example, in this scenario, T1 = 60s, T2 = 60s, and V = 5000mL can be set.

[0075] Normal usage scenario for the display unit: If a user turns on the display unit, they may need to view the currently recorded measurement data, requiring a relatively fast refresh of the measurement data. For example, in this scenario, T1 = 5s, T2 = 5s, and V = 100mL can be set.

[0076] In this embodiment of the application, when the display unit is not turned on, the smart metering device is in the normal use scenario where the display unit is not turned on. When the user turns on the display unit, the controller can send the metering data push strategy corresponding to the normal use scenario where the display unit is turned on to the metering device.

[0077] In this embodiment of the application, if the user turns on the display unit and does not operate the smart metering device within the time period of the screen-off duration after the last operation on the display unit, the display unit will automatically turn off. At this time, the controller can send the metering data push strategy corresponding to the normal use scenario where the display unit is not turned on to the metering device.

[0078] (3) Metering Boundary Value Prediction Scenario: For prepaid smart metering identification, the valve needs to be closed immediately when the balance equals 0 or the overdraft limit is exhausted, stopping user usage. In this scenario, metering data needs to be refreshed promptly so that the controller can be notified to close the valve at the critical point. The controller can receive the user's usage balance for the metered object sent by the balance detection module. If the user's balance is less than the preset balance, the controller can send the metering data push strategy corresponding to the metering boundary value prediction scenario to the metering device. For example, in this scenario, T1 = 5s, T2 = 1s, and V = 100mL can be set.

[0079] (4) Abnormal Event Scenarios: When the metering party detects an abnormal event, it needs to promptly notify the control party so that the control party can take appropriate action. For example, if the metering party detects that the current flow rate is too high, meaning that the rate of change of the metering data exceeds the safe rate of change within a certain period of time, and continued use may lead to serious consequences (such as pipeline overflow, which may cause an explosion), then an alarm message can be immediately sent to the control party so that the control party can take immediate action such as shutting off the valve to protect the user's interests. This alarm message may include the specific type of abnormal event.

[0080] The types of abnormal events in this application embodiment can include overcurrent events and magnetic interference events. An overcurrent event is an event where the rate of change of the metering data exceeds the safe rate of change; a magnetic interference event is an event where the metering data changes abnormally. A magnetic interference event can be defined as a situation where, within the anomaly detection period, the change in the metering data and / or the increment of the metering data meets the magnetic interference change condition.

[0081] In this embodiment of the application, the abnormal event can be denoted as E. It can be set to disable abnormal events in the table calibration scenario and not disable abnormal events in other scenarios.

[0082] Table 1 shows the metering configuration parameters for different application scenarios. The detailed descriptions of each parameter have been provided above and will not be repeated here.

[0083]

[0084] Table 1

[0085] The application scenario categories in this application embodiment may include, but are not limited to, the several scenarios mentioned above. Those skilled in the art can adaptively add different application scenarios.

[0086] Step S220: Obtain the actual measurement working parameters.

[0087] In this embodiment, the actual measurement parameters may include measurement duration and measurement data increment. The measurement duration is calculated by statistically analyzing the time interval during which the measurement data value remains unchanged. The measurement unit may include a measurement timer, which can be reset to zero when the measurement data value changes, and will continue timing if the measurement data value remains unchanged. The measurement duration in this embodiment may be denoted as Tn. For example, if the measurement data value is 1000mL and remains at 1000mL for 5 seconds, the measurement duration is also 5 seconds. When the measurement data value changes to 1005mL in the 6th second, the measurement duration will be reset to 0 seconds, i.e., timing will restart. When the measurement data value changes again, the measurement duration will be reset to 0 seconds again.

[0088] The increment of the measurement data refers to the increase in the measurement data over a certain period of time. In this embodiment, the increment of the measurement data can be denoted as Vn. For example, if the measurement data value is 1000 mL, and after 5 seconds it becomes 1200 mL, then the increment over that 5-second period is 200 mL. It should be noted that the magnitude of the increment needs to be considered in conjunction with a certain time duration.

[0089] Step S230: Based on the relationship between the actual metering working parameters and the metering configuration working parameters corresponding to the target metering data push strategy, push the metering data obtained by the metering to the control party.

[0090] The metering party can compare the actual metering operating parameters with the metering configuration operating parameters corresponding to the target metering data push strategy to determine the magnitude relationship between the two and whether it is necessary to push the metering data obtained from the metering to the control party. This relationship can include the relationship between Vn and V, and the relationship between Tn and T1 or T2.

[0091] Optionally, the metering party can calculate the rate of change of the metering data based on Vn and Tn in the actual metering working parameters, and can also push the metering data obtained by the metering party to the control party based on the rate of change of the metering data.

[0092] Optionally, the metering party can push the metering data obtained from the metering to the control party based on the magnitude change of the value of Vn in the actual metering working parameters.

[0093] Through the embodiments of this application, the metering unit can determine the relationship between the actual metering operating parameters and the metering configuration operating parameters according to different metering data push strategies, thereby deciding whether to push the metering data obtained from the metering to the control unit. This method can respond to different application scenario categories and provide different metering push methods, which is beneficial to improving the flexibility of the metering unit in pushing metering data.

[0094] Please see Figure 3 , Figure 3 A flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application. Figure 3 As shown, in an exemplary embodiment, the method for pushing the metering data can be as follows: Figure 1 The measurement method 120 shown is implemented, including steps S210 to S220 and steps S310 to S320.

[0095] Among them, steps S210 to S220 have been described in detail below. Figure 2 The embodiments shown are described in detail and will not be repeated here. Steps S310 to S320 will be described in detail below:

[0096] Step S310: Detect the current metering stage and determine the push conditions that match the metering stage based on the detected metering stage.

[0097] In this embodiment of the application, the metering stage may include an initial metering stage and a continuous metering stage.

[0098] The initial measurement phase refers to the period when the metering party is in a metering-stopped state and detects a change in the metering data for the first time at a certain moment. From that moment on, the metering party enters the initial measurement phase. The metering-stopped state is the state that the metering party enters when Tn reaches T1.

[0099] The continuous measurement phase refers to the period after the initial measurement phase, where the measurement party enters the continuous measurement phase if Tn has not reached T1.

[0100] The metering party can determine the push conditions that match the current metering stage.

[0101] Step S320: Based on the relationship between the actual metering working parameters and the metering configuration working parameters, and the push conditions, push the metering data obtained to the control party.

[0102] The metering party can push the metering data obtained from the metering to the control party when the relationship between the actual metering working parameters and the metering configuration working parameters meets the push conditions.

[0103] Using this method, the metering party can determine the push conditions based on the current metering stage. When the relationship between the actual metering working parameters and the metering configuration working parameters meets the push conditions, the metering data obtained by the metering party can be pushed to the control party, thus ensuring the accuracy of the metering data push.

[0104] Please see Figure 4 , Figure 4 A flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application. Figure 4 As shown, in an exemplary embodiment, the method for pushing the metering data can be as follows: Figure 1 The measurement method 120 shown is implemented including steps S210 to S220, steps S410 to S420, steps S430 to S440 and step S320.

[0105] Among them, steps S210 to S220 have been described in detail below. Figure 2 The illustrated embodiment describes step S320 in detail. Figure 3 The embodiments shown are described in detail and will not be repeated here. Steps S410 to S420 are described in detail below:

[0106] Step S410: If the metering duration reaches the first configured duration threshold, and a change in the metering data value is detected for the first time after the metering data value has not changed, then it is determined that the current stage is the initial metering stage.

[0107] If Tn reaches T1 and the measurement data value remains unchanged, the metering party can enter the metering stop state. Once in the metering stop state, the first detected change in the measurement data value indicates that the current measurement phase is in its initial stage. Here, Tn reaching T1 can mean that Tn is greater than or equal to T1.

[0108] It should be noted that if Tn = T1 and the measured data value remains unchanged, the metering party can enter the metering stop state. If Tn > T1 and the measured data value remains unchanged, the metering party will remain in the metering stop state.

[0109] Step S420: If the metering duration has not reached the first configured duration threshold, then it is determined that the current stage is continuous metering.

[0110] If Tn < T1, it means that the value of the measurement data has changed within T1, and the measurement party is in the continuous measurement stage.

[0111] Steps S430 to S440 will be described in detail below:

[0112] Step S430: If the current stage is the initial metering stage, the push condition is determined to be that the metering duration reaches the second configured duration threshold, or the metering data increment reaches the configured increment threshold, or the metering duration reaches the second configured duration threshold and the metering data increment reaches the configured increment threshold.

[0113] That is, if we are currently in the initial measurement phase, the push condition is: Tn reaches T2, or Vn reaches V; or Tn reaches T2 and Vn reaches V.

[0114] Step S440: If the current stage is continuous metering, the push condition is determined to be that the metering duration reaches the second configured duration threshold and the metering data increment reaches the configured increment threshold.

[0115] That is, if the current phase is continuous measurement, the push condition is: Tn reaches T2 and Vn reaches V.

[0116] It should be noted that after step S220 is completed, step S410 can be executed, followed by step S430; or, after step S220 is completed, step S420 can be executed, followed by step S440. The measurement party can execute the corresponding steps according to different situations, without needing to execute all steps from S410 to S440.

[0117] This method allows the metering party to determine its current metering stage, facilitating the determination of push conditions based on that stage. This ensures that the metering party only pushes metering data when the actual metering parameters meet the push conditions, guaranteeing the accuracy of the metering data push.

[0118] Please see Figure 5 , Figure 5 A flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application. Figure 5 As shown, in an exemplary embodiment, the method for pushing the metering data can be as follows: Figure 1 The measurement method 120 shown is implemented, including steps S210 to S220 and steps S510 to S520.

[0119] Among them, steps S210 to S220 have been described in detail below. Figure 2 The embodiments shown are described in detail, and will not be repeated here. Steps S510 to S520 are described in detail below:

[0120] Step S510: Detect whether any abnormal events occur based on the actual metering parameters; among which, abnormal events include overcurrent events and magnetic interference events.

[0121] Specifically, the metrology authority can determine whether abnormal events occur based on the abnormal detection duration and Vn detection parameters in the actual metrology work parameters.

[0122] Step S520: If an abnormal event is detected, the metering data obtained by the metering is pushed to the control party.

[0123] Optionally, in this step, in addition to pushing the metering data obtained from the metering to the control party, the metering party can also push alarm information, which may include the specific type of abnormal event, namely, overcurrent event or magnetic interference event.

[0124] In this embodiment of the application, the metering party can push alarm information to the control party under normal use scenarios and metering boundary value estimation scenarios, and the push of alarm information is not constrained by the metering configuration working parameters corresponding to the corresponding metering data push strategy.

[0125] This method allows the metering provider to send alarm information to the control provider when abnormal events occur, enabling the control provider to respond to the abnormal events, thereby protecting the safety of smart metering equipment and pipelines and minimizing the loss of user interests.

[0126] Please see Figure 6 , Figure 6 A flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application. Figure 6 As shown, in an exemplary embodiment, the method for pushing the metering data can be as follows: Figure 1 The measurement method 120 shown is implemented, including steps S210 to S220, steps S610 to S620 and step S520.

[0127] Among them, steps S210 to S220 have been described in detail below. Figure 2 The embodiments shown are described in detail, and will not be repeated here. Steps S610 to S620 are described in detail below:

[0128] Step S610: Calculate the rate of change of the metering data based on the metering data increment and the anomaly detection time. If the rate of change of the metering data is greater than the safe rate of change, then an overcurrent event is determined to have occurred.

[0129] Wherein, the rate of change of the measurement data = the increment of the measurement data / the anomaly detection duration, and the increment of the measurement data is the increment within the anomaly detection duration. The anomaly detection duration is the duration used to detect the anomaly event, and the rate of change of the safety data can be set by those skilled in the art; this application embodiment does not limit it.

[0130] For example, if the safe change rate is set to 1000 mL / s and the abnormal detection time is 5s, and the metering data increment is 5500 mL within those 5s, then the metering data change rate at this time = 5500 / 5 = 1100 mL / s > 1000 mL, then the metering party can determine that an overflow event has occurred.

[0131] Step S620: If the change in measurement data and / or the increment of measurement data meets the magnetic interference change condition within the anomaly detection period, then a magnetic interference event is determined to have occurred.

[0132] Optionally, the magnetic interference change condition can refer to a situation where, within a certain time period of the anomaly detection duration, the value of the measurement data at the end of that time period is not equal to the value of the measurement data at the beginning of that time period plus the increment of the measurement data within that time period. For example, in the time period from 1 second to 6 seconds, the measurement data is 1000 mL at 1 second and 2000 mL at 6 seconds, but the increment of the measurement data within that time period is 200 mL. Therefore, 2000 mL and 1200 mL are not equal, and this may indicate a magnetic interference event causing data recording disorder, which is considered a magnetic interference event.

[0133] Optionally, the change in magnetic interference condition can also refer to a situation where, during a certain period of the anomaly detection time, the measurement data and / or the increment of the measurement data changes from large to small. For example, if the measurement data is 11200 mL at 5 seconds and becomes 11000 mL at 10 seconds, that is, the measurement data has decreased, and therefore can be regarded as a magnetic interference event.

[0134] In the embodiments of this application, the magnetic interference change conditions can be designed by those skilled in the art, including but not limited to the two situations mentioned above, and are not limited here.

[0135] This method allows the metering party to detect whether any abnormal events have occurred based on the actual metering parameters, which helps ensure the safety of the equipment.

[0136] Please see Figure 7 , Figure 7 A flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application. Figure 7 As shown, in an exemplary embodiment, the method for pushing the metering data can be as follows: Figure 1 The measurement method 120 shown is implemented, including steps S210 to S220 and steps S710 to S720.

[0137] Among them, steps S210 to S220 have been described in detail below. Figure 2The embodiments shown are described in detail, and will not be repeated here. Steps S710 to S720 are described in detail below:

[0138] Step S710: Obtain the metering configuration working parameters from the target metering data push strategy.

[0139] Each time the controller receives metering data pushed by the metering provider, it can return a target metering data push strategy. In other words, each time the controller receives metering data, it can obtain the current application scenario category and, regardless of whether the application scenario category changes, send the target metering data push strategy corresponding to the current application scenario category to the metering provider. This target metering data push strategy includes metering configuration parameters, and different metering data push strategies may include different metering configuration parameters.

[0140] Step S720: Based on the relationship between the actual metering working parameters and the obtained metering configuration working parameters, push the metering data obtained by the metering to the control party.

[0141] The metering party can compare the actual metering operating parameters with the metering configuration operating parameters corresponding to the target metering data push strategy to obtain the relationship between the two, and determine whether it is necessary to push the metering data obtained by the metering to the control party.

[0142] Using this method, the controller can return the target metering data push strategy to the metering party each time it receives a push notification, thus ensuring the accuracy of the metering data pushed by the metering party.

[0143] Please see Figure 8 , Figure 8 A flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application. Figure 8 As shown, in an exemplary embodiment, the method for pushing the metering data can be as follows: Figure 1 The measurement method 120 shown is implemented, including steps S210 to S220 and steps S810 to S820.

[0144] Among them, steps S210 to S220 have been described in detail below. Figure 2 The embodiments shown are described in detail, and will not be repeated here. Steps S810 to S820 are described in detail below:

[0145] Step S810: Locate the metering configuration working parameters corresponding to the target metering data push strategy in the specified storage area; wherein, the specified storage area stores multiple metering data push strategies and the metering configuration working parameters corresponding to each of the multiple metering data push strategies.

[0146] Each time the controller receives metering data pushed by the metering provider, it can obtain the current application scenario category and check if the category has changed. If it has changed, the controller sends the target metering data push strategy corresponding to the current application scenario category to the metering provider. Upon receiving the target metering data push strategy, the metering provider can save it in a designated storage area and retrieve the corresponding metering configuration parameters. The metering provider can retrieve the metering configuration parameters corresponding to the target metering data push strategy from this designated storage area each time before pushing metering data to the controller.

[0147] Optionally, after the control party sends the target metering data push policy to the metering party, if the application scenario category changes and then reverts to the application scenario category corresponding to the target metering data push policy, the control party can send the identifier of the target metering data push policy to the metering party, enabling the metering party to retrieve the target metering data push policy from the designated storage area. This way, the control party does not need to resend the complete target metering data push policy, thus saving communication resources.

[0148] Step S820: Based on the relationship between the actual metering working parameters and the obtained metering configuration working parameters, push the metering data obtained by the metering to the control party.

[0149] The metering party can compare the actual metering operating parameters with the metering configuration operating parameters corresponding to the target metering data push strategy to obtain the relationship between the two, and determine whether it is necessary to push the metering data obtained by the metering to the control party.

[0150] This method eliminates the need for the controller to send the complete target metering data push strategy every time it receives a push notification from the metering provider, thus saving communication resources.

[0151] Figure 9 This is a flowchart illustrating a method for pushing metering data according to an exemplary embodiment. Figure 9 As shown, in an exemplary embodiment, the method may include steps S910 to S940, and the execution entity of this application embodiment may be as follows: Figure 1 The control unit 110 is shown. Steps S910 to S940 are described in detail below:

[0152] Step S910: Detect the current application scenario category.

[0153] The application scenario category can be input by the user, and the controller can provide several application scenario categories for the user to choose from.

[0154] Optionally, the application scenario category can also be identified by the controller. For example, when the user turns on the display unit, the controller can identify the current application scenario category as a normal usage scenario where the display unit is on. When the display unit is turned off, the controller can identify the current application scenario category as a normal usage scenario where the display unit is not on.

[0155] Step S920: Determine the target metering data push strategy that matches the detected application scenario category; wherein, the metering data push strategy is different for different application scenario categories.

[0156] The application scenario category and the target metering data push strategy are mapped together. This mapping relationship can be set by those skilled in the art and stored in the controller. The controller can obtain this mapping relationship and then determine the target metering data push strategy.

[0157] Step S930: Send the target metering data push strategy to the metering party so that the metering party can push the metering data obtained by metering to the control party according to the relationship between the actual metering working parameters and the metering configuration working parameters corresponding to the target metering data push strategy.

[0158] The target metering data push strategy includes metering configuration parameters. The metering party can compare the actual metering parameters with the metering configuration parameters corresponding to the target metering data push strategy to obtain the relationship between the two and determine whether it is necessary to push the metering data obtained by the metering party to the control party.

[0159] Step S940: Receive metering data sent by the metering party.

[0160] After receiving the metering data from the metering unit, the controller can update the metering data. If the display unit is on, the updated metering data can be displayed on the display unit for user viewing.

[0161] This method allows the controller to send corresponding metering data push strategies to the metering unit based on the detected application scenario category. This enables the metering unit to decide whether to push the obtained metering data to the controller based on the relationship between actual metering operating parameters and metering configuration operating parameters. This method improves the flexibility of metering data push.

[0162] Please see Figure 10 , Figure 10 A flowchart illustrating a method for pushing metering data, as shown in another exemplary embodiment of this application. Figure 10 As shown, in an exemplary embodiment, the method for pushing the metering data can be as follows: Figure 1The measurement method 120 shown is implemented, including steps S1010 to S1020 and steps S910 to S940.

[0163] Among them, steps S910 to S920 have been implemented as follows: Figure 9 The embodiments shown are described in detail, and will not be repeated here. Steps S1010 to S1020 are described in detail below:

[0164] Step S1010: Receive configuration instructions for each application scenario category. The configuration instructions include multiple metering configuration parameters.

[0165] The configuration instructions can be set by someone skilled in the art.

[0166] Step S1020: Associate each application scenario category with its corresponding multiple metering configuration parameters to obtain the metering data push strategy for each application scenario category.

[0167] This method allows for the association of various application scenario categories with multiple metering configuration parameters, enabling different metering data push strategies to correspond to different metering configuration parameters, thereby improving the flexibility of metering data push.

[0168] Figure 11 This is a flowchart illustrating a method for pushing metering data according to an exemplary embodiment. Figure 11 As shown, in an exemplary embodiment, the method may include steps S1110 to S1160, and the execution entity of this application embodiment may be as follows: Figure 1 The control unit 110 and the measurement unit 120 are shown. Steps S1110 to S1160 are described in detail below:

[0169] Step S1110: The controller detects the current application scenario category and determines the target metering data push strategy that matches the detected application scenario category.

[0170] Step S1120: The controller sends the target metering data push strategy to the metering party.

[0171] Step S1130: The metering party obtains the metering configuration working parameters from the target metering data push strategy.

[0172] Step S1140: The measurement party obtains the actual measurement working parameters.

[0173] Step S1150: The metering party detects the current metering stage and determines the push conditions that match the metering stage based on the detected metering stage.

[0174] Step S1160: The metering party pushes the metering data obtained from the metering to the control party based on the relationship between the actual metering working parameters and the metering configuration working parameters, and the push conditions.

[0175] The details of steps S1110 to S1160 have been described above and will not be repeated here.

[0176] This method helps to increase the flexibility of metering data delivery.

[0177] Figure 12 This is a schematic diagram illustrating the structure of a metering data delivery device according to an exemplary embodiment. For example... Figure 12 As shown, in an exemplary embodiment, the device for pushing metering data includes:

[0178] The transceiver unit 1210 is used to receive the target metering data push strategy sent by the controller; wherein, the target metering data push strategy is a strategy determined by the controller based on the detected current application scenario category and matched with the application scenario category, and the metering data push strategy is different for different application scenario categories.

[0179] Acquisition unit 1220 is used to acquire actual measurement working parameters;

[0180] The transceiver unit 1210 is also used to push the metering data obtained from the metering to the control party based on the relationship between the actual metering working parameters and the metering configuration working parameters corresponding to the target metering data push strategy.

[0181] In one embodiment of this application, based on the aforementioned scheme, the detection unit 1230 is used to detect the current metering stage and determine the push conditions matching the metering stage according to the detected metering stage; the transceiver unit 1210 is also used to push the metering data obtained by metering to the controller according to the relationship between the actual metering working parameters and the metering configuration working parameters and the push conditions.

[0182] In one embodiment of this application, based on the aforementioned scheme, the actual metering working parameters include metering duration, which is obtained by statistically analyzing the time period corresponding to the period when the value of the metering data does not change. The metering configuration working parameters include a first configuration duration threshold, which is used to characterize the time period threshold when the value of the metering data does not change. The processing unit 1240 is used to determine that the current stage is in the initial metering stage if the metering duration reaches the first configuration duration threshold and a change in the value of the metering data is detected for the first time after the value of the metering data has not changed; and to determine that the current stage is in the continuous metering stage if the metering duration does not reach the first configuration duration threshold.

[0183] In one embodiment of this application, based on the aforementioned scheme, the actual metering working parameters further include metering data increment, and the metering configuration working parameters further include a second configuration duration threshold and a configuration increment threshold. The second configuration duration threshold is used to characterize the time interval at which metering data should be pushed, and the configuration increment threshold is used to characterize the increment that the pushed metering data should reach. The processing unit 1240 is further configured to determine the push condition as follows if the current state is in the initial metering stage: the metering duration reaches the second configuration duration threshold, or the metering data increment reaches the configuration increment threshold, or the metering duration reaches the second configuration duration threshold and the metering data increment reaches the configuration increment threshold; if the current state is in the continuous metering stage, the push condition is determined as the metering duration reaches the second configuration duration threshold and the metering data increment reaches the configuration increment threshold.

[0184] In one embodiment of this application, based on the aforementioned scheme, the metering configuration working parameters include abnormal events; the processing unit 1240 is further configured to detect whether an abnormal event occurs according to the actual metering working parameters; wherein, the abnormal events include overcurrent events and magnetic interference events; the transceiver unit 1210 is further configured to push the metering data obtained by the metering to the control party if an abnormal event is detected.

[0185] In one embodiment of this application, based on the aforementioned scheme, the processing unit 1240 is further configured to calculate the rate of change of the metering data based on the metering data increment and the metering duration; if the rate of change of the metering data is greater than the safe rate of change, then an overcurrent event is determined to have occurred; if, within the metering duration, the amount of change of the metering data and / or the metering data increment meets the magnetic interference change condition, then a magnetic interference event is determined to have occurred.

[0186] In one embodiment of this application, based on the aforementioned scheme, the target metering data push strategy includes metering configuration working parameters; the processing unit 1240 is further configured to obtain the metering configuration working parameters from the target metering data push strategy; the transceiver unit 1210 is further configured to push the metering data obtained by the metering to the control party according to the relationship between the actual metering working parameters and the obtained metering configuration working parameters.

[0187] In one embodiment of this application, based on the aforementioned scheme, the processing unit 1240 is further configured to search for the metering configuration working parameters corresponding to the target metering data push strategy from a designated storage area; wherein, the designated storage area stores multiple metering data push strategies and metering configuration working parameters corresponding to the multiple metering data push strategies respectively; the transceiver unit 1210 is further configured to push the metering data obtained by the metering to the control party according to the relationship between the actual metering working parameters and the obtained metering configuration working parameters.

[0188] In one exemplary embodiment, the device for pushing metering data further includes:

[0189] Detection unit 1230 is used to detect the current application scenario category;

[0190] The processing unit 1240 is used to determine a target metering data push strategy that matches the detected application scenario category; wherein, the metering data push strategy is different for different application scenario categories.

[0191] The transceiver unit 1210 is used to send the target metering data push strategy to the metering party, so that the metering party can push the metering data obtained by metering to the control party according to the relationship between the actual metering working parameters and the metering configuration working parameters corresponding to the target metering data push strategy.

[0192] The transceiver unit 1210 is also used to receive metering data sent by the metering party.

[0193] In one embodiment of this application, based on the aforementioned scheme, the transceiver unit 1210 is further configured to receive configuration instructions for each application scenario category before detecting the current application scenario category, the configuration instructions including multiple metering configuration working parameters; the processing unit 1240 is further configured to associate each application scenario category with the corresponding multiple metering configuration working parameters to obtain the metering data push strategy corresponding to each application scenario category.

[0194] It should be noted that the metering data push device provided in the above embodiments and the metering data push method provided in the above embodiments belong to the same concept. The specific way in which each module and unit performs operations has been described in detail in the method embodiments, and will not be repeated here.

[0195] Embodiments of this application also provide an electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by one or more processors, enable the electronic device to implement the metering data push method provided in the above embodiments.

[0196] Figure 13 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown.

[0197] It should be noted that, Figure 13 The computer system 1300 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0198] like Figure 13As shown, the computer system 1300 includes a Central Processing Unit (CPU) 1301, which can perform various appropriate actions and processes, such as executing the methods described in the above embodiments, based on programs stored in Read-Only Memory (ROM) 1302 or programs loaded from storage portion 1308 into Random Access Memory (RAM) 1303. The RAM 1303 also stores various programs and data required for system operation. The CPU 1301, ROM 1302, and RAM 1303 are interconnected via a bus 1304. An Input / Output (I / O) interface 1305 is also connected to the bus 1304.

[0199] The following components are connected to I / O interface 1305: an input section 1306 including a keyboard, mouse, etc.; an output section 1307 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1308 including a hard disk, etc.; and a communication section 1309 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 1309 performs communication processing via a network such as the Internet. A drive 1310 is also connected to I / O interface 1305 as needed. Removable media 1311, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1310 as needed so that computer programs read from them can be installed into storage section 1308 as needed.

[0200] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1309, and / or installed from removable medium 1311. When the computer program is executed by central processing unit (CPU) 1301, it performs various functions defined in the system of this application.

[0201] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. For example, a computer-readable medium can be an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable medium may include, but are not limited to: an electrical connection having 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), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

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

[0203] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0204] Another aspect of this application provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the cross-domain data transfer method as described above. This computer-readable medium may be included in the electronic device described in the above embodiments, or it may exist independently and not assembled into the electronic device.

[0205] Another aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable medium. A processor of a computer device reads the computer instructions from the computer-readable medium and executes the computer instructions, causing the computer device to perform the cross-domain data transfer method provided in the various embodiments described above.

[0206] The above description is merely a preferred exemplary embodiment of this application and is not intended to limit the implementation of this application. Those skilled in the art can easily make corresponding modifications or alterations based on the main concept and spirit of this application. Therefore, the scope of protection of this application should be determined by the scope of protection claimed in the claims.

Claims

1. A method for pushing measurement data, characterized in that, include: The system receives a target metering data push strategy sent by the control party; wherein the target metering data push strategy is a strategy determined by the control party based on the detected current application scenario category and matched with the application scenario category, and different application scenario categories correspond to different metering data push strategies. Obtain actual metering working parameters, which include metering data increment and metering duration. The metering duration is obtained by statistically analyzing the time period corresponding to when the value of the metering data does not change. Based on the relationship between the actual metering working parameters and the metering configuration working parameters corresponding to the target metering data push strategy, the metering data obtained by metering is pushed to the control party. The metering configuration working parameters include a first configuration duration threshold, a second configuration duration threshold, and a configuration increment threshold. The first configuration duration threshold is used to characterize the time period threshold during which the value of the metering data does not change. The second configuration duration threshold is used to characterize the time interval at which the metering data should be pushed. The configuration increment threshold is used to characterize the increment that the metering data should reach. The step of pushing the metering data obtained from metering to the control party based on the relationship between the actual metering operating parameters and the metering configuration operating parameters corresponding to the target metering data push strategy includes: If the metering duration reaches the first configured duration threshold, and a change in the metering data value is detected for the first time after the metering data value has not changed, then it is determined that the current stage is the initial metering stage. If the metering duration does not reach the first configured duration threshold, it is determined that the current stage is continuous metering. If the current stage is the initial metering stage, the push condition is determined to be that the metering duration reaches the second configured duration threshold, or the metering data increment reaches the configured increment threshold, or the metering duration reaches the second configured duration threshold and the metering data increment reaches the configured increment threshold. If the current phase is continuous metering, the push condition is determined to be that the metering duration reaches the second configured duration threshold and the metering data increment reaches the configured increment threshold. Based on the relationship between the actual metering operating parameters and the metering configuration operating parameters, and the push conditions, the metering data obtained is pushed to the control party.

2. The method according to claim 1, characterized in that, The metering configuration parameters include abnormal events; the step of pushing the obtained metering data to the control party based on the relationship between the actual metering parameters and the metering configuration parameters corresponding to the target metering data push strategy includes: The abnormal event is detected based on the actual metering operating parameters; wherein the abnormal event includes at least one of an overcurrent event and a magnetic interference event; If an abnormal event is detected, the metering data obtained from the metering is pushed to the control party.

3. The method according to claim 2, characterized in that, The actual metering working parameters include metering data increments, and the metering configuration working parameters include anomaly detection duration; the anomaly detection duration is the duration used to detect the anomaly event. The step of detecting whether the abnormal event has occurred based on the actual measurement working parameters includes: The rate of change of the metering data is calculated based on the metering data increment and the anomaly detection duration. If the rate of change of the metering data is greater than the safe rate of change, then the overcurrent event is determined to have occurred. If, within the anomaly detection period, the change in the measurement data and / or the increment of the measurement data meets the magnetic interference change condition, then the magnetic interference event is determined to have occurred.

4. The method according to any one of claims 1 to 3, characterized in that, The target metering data push strategy includes the metering configuration working parameters; the step of pushing the metering data obtained from metering to the control party based on the relationship between the actual metering working parameters and the metering configuration working parameters corresponding to the target metering data push strategy includes: Obtain the metering configuration working parameters from the target metering data push strategy; Based on the relationship between the actual metering operating parameters and the obtained metering configuration operating parameters, the metering data obtained by the metering is pushed to the control party.

5. The method according to any one of claims 1 to 3, characterized in that, The step of pushing the metering data obtained from metering to the control party based on the relationship between the actual metering operating parameters and the metering configuration operating parameters corresponding to the target metering data push strategy includes: The metering configuration parameters corresponding to the target metering data push strategy are retrieved from the specified storage area; wherein, the specified storage area stores multiple metering data push strategies and metering configuration parameters corresponding to each of the multiple metering data push strategies. Based on the relationship between the actual metering operating parameters and the obtained metering configuration operating parameters, the metering data obtained by the metering is pushed to the control party.

6. A method for pushing measurement data, characterized in that, include: Detect the current application scenario category; Based on the detected application scenario category, a target metering data push strategy matching the application scenario category is determined; wherein, different application scenario categories correspond to different metering data push strategies; The target metering data push strategy is sent to the metering party, so that the metering party pushes the metering data obtained from the metering to the control party according to the relationship between the actual metering working parameters and the metering configuration working parameters corresponding to the target metering data push strategy. The actual metering working parameters include metering data increment and metering duration. The metering duration is obtained by statistically analyzing the time period corresponding to the period when the metering data value does not change. The metering configuration working parameters include a first configuration duration threshold, a second configuration duration threshold, and a configuration increment threshold. The first configuration duration threshold is used to characterize the time period threshold for when the metering data value does not change. The second configuration duration threshold is used to characterize the time interval at which metering data should be pushed. The configuration increment threshold is used to characterize the increment that the pushed metering data should achieve. Receive the measurement data sent by the measurement party; The step of pushing the metering data obtained from metering to the control party based on the relationship between the actual metering operating parameters and the metering configuration operating parameters corresponding to the target metering data push strategy includes: If the metering duration reaches the first configured duration threshold, and a change in the metering data value is detected for the first time after the metering data value has not changed, then it is determined that the current stage is the initial metering stage. If the metering duration does not reach the first configured duration threshold, it is determined that the current stage is continuous metering. If the current stage is the initial metering stage, the push condition is determined to be that the metering duration reaches the second configured duration threshold, or the metering data increment reaches the configured increment threshold, or the metering duration reaches the second configured duration threshold and the metering data increment reaches the configured increment threshold. If the current phase is continuous metering, the push condition is determined to be that the metering duration reaches the second configured duration threshold and the metering data increment reaches the configured increment threshold. Based on the relationship between the actual metering operating parameters and the metering configuration operating parameters, and the push conditions, the metering data obtained is pushed to the control party.

7. The method according to claim 6, characterized in that, Before detecting the current application scenario category, the method further includes: Receive configuration instructions for various application scenario categories, the configuration instructions including multiple metering configuration working parameters; Each application scenario category is associated with its corresponding multiple metering configuration parameters to obtain the metering data push strategy for each application scenario category.

8. A device for pushing metering data, characterized in that, include: The transceiver unit is used to receive the target metering data push strategy sent by the controller; wherein, the target metering data push strategy is a strategy determined by the controller based on the detected current application scenario category and matched with the application scenario category, and the metering data push strategy is different for different application scenario categories. The acquisition unit is used to acquire actual metering working parameters, which include metering data increment and metering duration. The metering duration is obtained by statistically analyzing the time period corresponding to when the value of the metering data has not changed. The transceiver unit is further configured to push the metering data obtained by the metering to the control party according to the relationship between the actual metering working parameters and the metering configuration working parameters corresponding to the target metering data push strategy. The metering configuration working parameters include a first configuration duration threshold, a second configuration duration threshold, and a configuration increment threshold. The first configuration duration threshold is used to characterize the time period threshold during which the value of the metering data does not change. The second configuration duration threshold is used to characterize the time interval during which the metering data should be pushed. The configuration increment threshold is used to characterize the increment that the metering data should reach. The step of pushing the metering data obtained from metering to the control party based on the relationship between the actual metering working parameters and the metering configuration working parameters corresponding to the target metering data push strategy includes: if the metering duration reaches the first configured duration threshold, and a change in the metering data value is detected for the first time after the metering data value has not changed, then it is determined that the current stage is the initial metering stage; if the metering duration does not reach the first configured duration threshold, then it is determined that the current stage is the continuous metering stage; if the current stage is the initial metering stage, then the push condition is determined to be that the metering duration reaches the second configured duration threshold, or the metering data increment reaches the configured increment threshold, or the metering duration reaches the second configured duration threshold and the metering data increment reaches the configured increment threshold; if the current stage is the continuous metering stage, then the push condition is determined to be that the metering duration reaches the second configured duration threshold and the metering data increment reaches the configured increment threshold; and the metering data obtained from metering is pushed to the control party based on the relationship between the actual metering working parameters and the metering configuration working parameters and the push condition.

9. An electronic device, characterized in that, include: One or more processors; A memory for storing one or more programs, which, when executed by the electronic device, cause the electronic device to implement the method for pushing metering data as described in any one of claims 1 to 5, or to implement the method for pushing metering data as described in any one of claims 6 to 7.

10. A computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the method for pushing measurement data as described in any one of claims 1 to 5, or the method for pushing measurement data as described in any one of claims 6 to 7.

Images